Jason R. Coombs
Jason R. Coombs
In the latest commit, I've consolidated the compatibility logic into its own module, a module that clearly indicates its candidacy for removal after Python 3.9 is dropped.
Now the tests are failing with `twine/__init__.py:48: error: Module has no attribute "parseaddr" [attr-defined]`. But this diff doesn't alter that behavior. Hmm. It seems to be an error in mypy....
While revisiting #633, I observed that setting `PIP_DEFAULT_PYTHON` (https://github.com/pypa/pipx/issues/633#issuecomment-1501212124) appears to work around this issue too. After setting it to `$(which python3)`, the error goes away and `pipx reinstall-all` now...
Closing as a duplicate of #10590 and #12070.
In #4116, I expressed: This issue is still needed and still a blocker to remove the suboptimal hack in pip-run that attempts to do the same thing (https://github.com/jaraco/pip-run/issues/51). Is there...
> [Since pip 23.1](https://pip.pypa.io/en/stable/news/#v23-1) we don't use `setup.py` install for legacy projects, we do a build using an isolated environment. It's _that_ build (which is a subprocess) that needs setuptools...
The issue appears to be a permissions one. The error only occurs when running not as Administrator.
The issue too only seems to affect the executable wrapper. The package itself remains installed after the failed attempt. ``` PS C:\Users\jaraco> py -m pip uninstall -y pip-run Found existing...
Does this change address any of the open issues?
This change has been merged into the 7.8.0 release of [calendra](https://pypi.org/project/calendra).