Closed regiontog closed 3 months ago
Odd. According to the project description (https://pypi.org/project/typing/) it says that typing should be shadowed automatically by the system's version if present, except in when using pip install -t .
; does that describe your case?
For package maintainers, it is preferred to use
typing;python_version<"3.5"
if your package requires it to support earlier Python versions. This will avoid shadowing the stdlib typing module when your package is installed viapip install -t .
on Python 3.5 or later.
However, this is probably just a good thing to explicitly state anyway. If you change the version to 3.5
I'll probably merge this ASAP.
That is a little strange yeah, I'm guessing it has something to do with the python provided by nix(which I use to manage dev environments). I used pip install -r requirements.txt
to install draftsman. If you'd like I could probably setup a minimal reproducible nix flake. But from my pov this should not be a problem anymore :)
I updated to 3.5 :D
Hello, thank you for this package! I'm getting some strange errors after installing it and from what I can tell it seems to be related to the package
typing
on newer versions of python. I looked in your procjects requirements.txt and there seems to be a guard so I was a little bit confused as I have python 3.10. But digging a bit further this guard seems suspiciously absent in setup.py. I verified it works with this patch on my system, but I really don't have good enought of a mental model of pythons package system to say anything about whether this is the right thing, hopefully its on the right track.Here is the original error:
And the logs from a clean install of your package v1.1.1