Breakout pip._internal.download to a pip._internal.network sub-package
See original GitHub issuepip._internal.download
is almost 1200 LoC.
It’d probably make sense to break it up into smaller modules in a pip._internal.network
package.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
AttributeError: module 'pip._internal.download' has no attribute ...
This appears to be because you installed the pip-system-certs package, which hooks into pip internals in a way that was never supported.
Read more >Pip is not working: ImportError: No module named 'pip._internal'
After upgrading pip (or pip3 , in this case) if the following occurs: $ ~ pip3 -V Traceback (most recent call last): File ......
Read more >Dependencies & vendoring - Google Groups
In Google's internal source tree, we vendor (copy) all our dependencies into our source tree and have at most one copy of any...
Read more >Overview | Adafruit MagTag
This WROVER module comes with 4 MB flash and 2 MB PSRAM. The 4 MB of flash is inside the module and is...
Read more >2019-October.txt - SuSE Lists
Description: This update for python-jmespath, python-jsonschema, python-paramiko, python-pexpect, python-pip, python-ply, python-pretend, ...
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
#7045 #7062 #7089
Just, like, I think we should not have a download.py module on the top level when we also have a network sub-package.
It’s more of preferences than something technical.