Search Criteria
Package Details: mypy-git 1.9.0.r40.ga00fcba-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/mypy-git.git (read-only, click to copy) |
---|---|
Package Base: | mypy-git |
Description: | Optional static typing for Python 2 and 3 (PEP484) |
Upstream URL: | https://github.com/JukkaL/mypy |
Keywords: | development |
Licenses: | MIT |
Conflicts: | mypy |
Provides: | mypy |
Submitter: | eigengrau |
Maintainer: | xiota |
Last Packager: | xiota |
Votes: | 12 |
Popularity: | 0.000000 |
First Submitted: | 2015-10-02 07:27 (UTC) |
Last Updated: | 2024-03-13 20:20 (UTC) |
Dependencies (8)
- python-mypy_extensions
- python-psutil
- python-tomli
- python-typing_extensions
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-setuptools (make)
- python-wheel (make)
Required by (63)
- chalice (requires mypy) (make)
- dpsprep-git (requires mypy) (check)
- emacs-flycheck-pycheckers (requires mypy) (optional)
- fluster (requires mypy) (make)
- freenom-dns-updater (requires mypy) (check)
- harlequin (requires mypy)
- keyringctl-git (requires mypy) (check)
- metadata-cleaner (requires mypy) (check)
- metainfo-builder-git (requires mypy) (check)
- nbqa (requires mypy) (check)
- nbqa (requires mypy) (optional)
- neovim-coc-pyright-git (requires mypy) (optional)
- nrf-connect-sdk-installer (requires mypy) (optional)
- ocaml-atd (requires mypy) (check)
- ocaml-atdgen (requires mypy) (check)
- ocaml-atdgen-codec-runtime (requires mypy) (check)
- ocaml-atdgen-runtime (requires mypy) (check)
- ocaml-atdj (requires mypy) (check)
- ocaml-atdpy (requires mypy) (check)
- ocaml-atds (requires mypy) (check)
- Show 43 more...
Latest Comments
1 2 3 Next › Last »
gesh commented on 2024-03-13 12:53 (UTC)
Fair enough
xiota commented on 2024-03-13 11:59 (UTC)
What you wrote demonstrates the problems with using "(n+1)+dev" and other non-monotonic versioning schemes. There is no such release version, yet. Dropping or overlooking the +dev suffix is too easy, making discussions about versions confusing.
gesh commented on 2024-03-13 11:07 (UTC)
Ah, correct -- I had attempted to manually run the commands, which obviously caused some trouble. Sorry for the noise.
Fair enough in re the discussion being academic -- though if you want, I think you could try requesting it be orphaneed.
In re
1.10.0
being an invalid base number -- not sure that's up to us to decide. If upstream wants to number its versions1.9
,1.10+dev
,1.10
, then we should use that (barring this breaking vercmp or the pkgver format). Though I am unsure how to ensure that in this case -- appending a string to a version generally can't make a smaller version. Perhaps by making sure the version string is always of formBASE_VER-dev.rN.gSHA
?Regardless, that's up to you -- my only interest in the package was for trying out mypy 1.10 to make sure an error I was seeing was due to the code and not due to upstream using 1.9 while repos have 1.8.
xiota commented on 2024-03-12 23:02 (UTC) (edited on 2024-03-12 23:13 (UTC) by xiota)
None of the commands in the
pkgver()
function I suggested produce that argument. Looks like you are running different commands or have left over junk in yoursrc
folder. Build in clean chroot or delete oldsrc
andpkg
directories.Here is an excerpt of output from
makepkg -Cf
(no error):Notes:
git checkout...
) won't work because it produces output besides the version string.mypy.version
produces wrong version string1.10.0.r38.gea49e1f
. There is no released/tagged version 1.10.0.gesh commented on 2024-03-12 17:43 (UTC) (edited on 2024-03-12 17:47 (UTC) by gesh)
That doesn't work -- the release tags are off the mainline branch, so am getting
If you really insist, you could do:
Or you could fixup the rendering of the version as given by
version.py
:xiota commented on 2024-03-12 16:56 (UTC) (edited on 2024-03-12 23:05 (UTC) by xiota)
Using
mypy.version
produces version strings with the wrong format:1.10.0+dev.ea49e1fa488810997d192a36d85357dadb4a7f14
I would suggest the following, which produces
1.9.0.r39.gea49e1f
:This package also needs to be updated to PEP 517 install method.
gesh commented on 2024-03-12 16:27 (UTC)
In case anyone needs it, this
version()
works:eigengrau commented on 2019-04-27 14:12 (UTC)
@alex.shpilkin Thank you for the pointer. As for the version tag: it’s not picked up because newer release tags were only assigned to release commits not merged into the master branch. It also seems that it’s still a bit awkward running both mypy and mypy-extensions from their respective master branches, since mypy pins its mypy-extensions requirement to a distribution version not supplied by mypy-extensions when built from git (one would need to patch mypy’s setup.py).
Since mypy is part of the community repo now I’m orphaning the package. In case anyone needs the dev build feel free to take over.
alex.shpilkin commented on 2019-04-27 10:53 (UTC)
This does not build in a clean chroot (e.g. using aurutils), complaining about missing 'setuptools' (missing python-setuptools dependency?). The version is also not picked up correctly from the source code for some reason: my mypy-git build from post-0.700 sources still claims to be 0.520.r1256.
1 2 3 Next › Last »