Move all of pip's CLI handling into `pip._internal.cli`
See original GitHub issue- Allows us to break up
pip._internal.__init__
- Provides a clearer place to put all of the autocompletion support code.
- Better grouping of the code that does one thing
Suggested rearrangement (I’ll omit pip._internal
and say pip
instead):
before | after |
---|---|
pip.__init__.autocomplete() |
pip.cli.autocompletion.autocomplete() |
pip.basecommand |
pip.cli.basecommand |
pip.baseparser |
pip.cli.option_parser |
pip.cmdoptions |
pip.cli.option_templates |
pip.commands |
pip.cli.commands |
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Using Python's pip to Manage Your Projects' Dependencies
In this beginner-friendly tutorial, you'll learn how to use pip, ... Using pip inside a virtual environment has three main advantages.
Read more >No module named 'pip._internal.cli.main' - Stack Overflow
Run the following command to solve the problem. $ conda install -c conda-forge pip.
Read more >pip install - pip documentation v22.3.1
Upgrade all specified packages to the newest available version. The handling of dependencies depends on the upgrade-strategy used. --upgrade-strategy < ...
Read more >Python PIP - W3Schools
Open the command line interface and tell PIP to download the package you want. Navigate your command line to the location of Python's...
Read more >How to Fix 'Pip' is Not Recognized as an Internal or External ...
Press the Windows key + R to open Run. · Type cmd and then press Enter for the command prompt. · For a...
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 Free
Top 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
@techalchemy Could you please at least add a huge disclaimer to the docs that makes it clear that the pip maintainers take no responsibility for any breakage as a result of using this package?
(Giant warning added btw)