-
Notifications
You must be signed in to change notification settings - Fork 385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'? #1368
Comments
The problem is:
The 3.10 site-packages is sneaking in there, and I don't see how. It's only in the pipx venv Python, but pyvenv.cfg seems fine, etc. More info at tomerfiliba/plumbum#678. |
Any updates on the issue so far? Also thanks for attempts to fix it on plumbum side @henryiii , let me know if you need help testing out that draft pr in codespaces 👍 |
Same issue here. Install v1.5.0 via brew and getting this when trying to pipx install poetry |
Describe the bug
The following repo was specifically created to outline a reproducible environment with the bug https://github.com/aorumbayev/pipx_bug.
I am not sure of the root cause but it is something to do with the way pipx uses shared venv and running pipx installed executable python modules that have
copier
package as transitive dependency installed for target py >=3.12 while pipx itself is installed with py <3.12.I also opened this issue on copier repo copier where copier maintainers forwarded me to also open an issue on plumbum transitive dependency that they rely on (and which throws the error) -> available here tomerfiliba/plumbum#678. Yet, still opening the issue on pipx repo as well given that copier maintainers also suspect that something may be wrong with the way shared venv is reused by pipx. Based on logs pipx is somehow able to access packages across multiple venvs. The issue is easily reproduced on github codespaces or github actions (use ubuntu-latest workers). If you have pipx installed locally on your machine and it was installed using 3.12 as a base python - everything works just fine (because the shared venv on pipx side is also using 3.12 in that case).
Logs
How to reproduce
Refer to readme on https://github.com/aorumbayev/pipx_bug
Expected behavior
Executing packages via pipx on >=3.12 should defer to 3.12 based shared venv
The text was updated successfully, but these errors were encountered: