Search Criteria
Package Details: python-pylsp-mypy 0.6.9-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/python-lsp-mypy.git (read-only, click to copy) |
---|---|
Package Base: | python-lsp-mypy |
Description: | Static type checking for python-lsp-server with mypy |
Upstream URL: | https://github.com/python-lsp/pylsp-mypy |
Licenses: | MIT |
Conflicts: | python-lsp-mypy |
Provides: | python-lsp-mypy |
Replaces: | python-lsp-mypy |
Submitter: | wuestengecko |
Maintainer: | wuestengecko |
Last Packager: | wuestengecko |
Votes: | 8 |
Popularity: | 0.65 |
First Submitted: | 2021-08-19 13:12 (UTC) |
Last Updated: | 2024-09-03 17:23 (UTC) |
Dependencies (8)
- mypy (mypy-gitAUR)
- python-lsp-server
- python-toml (python-toml-gitAUR)
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-setuptools (make)
- python-wheel (make)
- python-pytest (check)
Latest Comments
wuestengecko commented on 2023-12-08 15:49 (UTC)
Seems it's the same known issue with a user-wide
.config/mypy/config
file again, the unit tests don't really like that.I've pushed an updated PKGBUILD that just ignores this failure.
emilylime commented on 2023-12-08 14:13 (UTC)
The package fails to build with this output: https://pastebin.com/mXTFPuuY (specifically, tests are failing)
wuestengecko commented on 2023-04-05 12:56 (UTC)
This could actually exactly be caused by the
pip install
– I presume that at some point youpip install
-ed something which pulled in fastjsonschema with the then-current version, but that's outside of pacman's control and so cannot be updated by it. When pacman later installed python-fastjsonschema-2.16.3 system-wide, it was "hidden" by your earlier, user-specific pip install. Take a look at your~/.local/lib/python3.10
, you probably have quite a few packages installed there by now. (This is a similar reason to why "sudo pip install" without a virtualenv warns you, but there's no such warning without sudo.)That's an issue with the unit test. I've reported it upstream: https://github.com/python-lsp/pylsp-mypy/issues/59
For the time being, you can ignore the error with
makepkg --nocheck
.doct0rhu commented on 2023-04-04 02:34 (UTC) (edited on 2023-04-04 02:47 (UTC) by doct0rhu)
See the following error
This is weird. I've also seen this error when installing another package (python-sexpdata). But is solved by
pip install "fastjsonschema>=2.16.2"
.Then it fails during building stage:
wuestengecko commented on 2022-04-22 14:24 (UTC)
Thanks, changed it.
You're right, it makes the most sense to just directly follow upstream with this.
rnestler commented on 2022-03-16 14:05 (UTC)
The upstream URL seems to have changed to https://github.com/python-lsp/pylsp-mypy.
Also the package seems to be named pylsp-mypy not lsp-mypy.