Pip3 freeze outputs Could not parse requirement: -BB
See original GitHub issue- Pip version: 19.0.3
- Python version: 3.7.3
- Operating system: MacOS 10.14.4
I am trying to clean a bit my system-wide pip3 package to move all the development to the respective virtual environments.
I managed to remove all the pip3 packages, but right now I am getting such output for pip3 freeze:
➜ ~ pip3 freeze
Could not parse requirement: -BB
What can be the reason for such output?
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
pip install -r requirements.txt - can't parse python_version ...
Same problem for me and I cannot upgrade pip with the command given by @Forge: pip install --upgrade pip root@1c86632c84e6:/# pip install ...
Read more >WARNING: Could not parse requirement: -ython - Reddit
When doing this pip freeze > requirements.txt WARNING: Could not parse requirement: -ython Google does not find anything, it looks like a ...
Read more >pip freeze - pip documentation v22.3.1
If in a virtualenv that has global access, do not output globally-installed packages. --user#. Only output packages installed in user-site.
Read more >IO tools (text, CSV, HDF5, …) — pandas 1.5.2 documentation
Parsing a CSV with mixed timezones#. pandas cannot natively represent a column or index with mixed timezones. If your CSV file contains columns...
Read more >Release 3.3.0 holger krekel and others - tox Documentation
details and will not recreate or re-install dependencies. ... https://pip.pypa.io/en/stable/user_guide/#requirements-files.
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
You are exactly right, they were a residue after TBB package. Thank you for your help!
I think those directories exist because of a bug in an earlier version of pip (maybe in 19.0.1 / 19.0.2). You can think of them as temp directories that got created while installing / uninstalling something, but they were orphaned / not cleaned up correctly. The “~” character replaced some other character, so it might have been something like “ABB” or “BBB” originally. It’s okay to delete them. If you’re curious, you can also look inside to try and figure out what package they corresponded to.