Packages with . in their name are no longer install-able - Internal Error
See original GitHub issueThis worked a few months ago, but now it fails. For example:
pipx install kreagroup.jsi18n Internal error with venv metadata inspection.
Unable to install kreagroup-jsi18n.
Check the name or spec for errors, and verify that it can be installed with pip.
@itsayellow any ideas about why this could be?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Xcode 13.2 - Internal error : Miss… | Apple Developer Forums
I installed the additional components, and my project won't compile anymore : Xcode just tells me "Internal error: missingPackageDescriptionModule - Resolving ...
Read more >Showing error in yarn start command says This package ...
It means a certain package is not installed, and you need to install it. Try running yarn ...
Read more >How to fix E: Internal Error, No file name for libc6 - Ask Ubuntu
I know this is as old thread, but I encountered this problem recently during an upgrade of 12.04 LTS. None of the solutions...
Read more >Product Package Name in IBM Installation Manager shows as ...
An internal error occurred during: "Uninstall Packages". java.lang.IllegalStateException: No metadata found for installed IU com.ibm.rad.
Read more >Troubleshooting Windows Subsystem for Linux | Microsoft Learn
Provides detailed information about common errors and issues people run into while running Linux on the Windows Subsystem for Linux.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
OK I guess this is the same as bug #528 .
I thought
venv_metadata_inspector.py
was properly handling canonicalized names, but apparently not yet. I guess this just means I have to get my PR submitted with the update tovenv_metadata_inspector.py
.#593 will be landing soon, and should take care of this.