IPython 8.0 requires pre-release dependency
See original GitHub issueWith the release of IPython 8.0 it is now dependent on black
, which has all releases on pypi marked as pre-release, that means, e.g. you cannot install IPython 8.0 with pipenv without enabling pre-release dependencies even tho IPython is not pre-release.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:10 (3 by maintainers)
Top Results From Across the Web
How to install pre-release python packages in setup.py ...
setuptools doesn't install dependencies — pip installs them (or easy_install ). Use command line switch pip install --pre to allow ...
Read more >PEP 440 – Version Identification and Dependency Specification
This PEP describes a scheme for identifying versions of Python software distributions, and declaring dependencies on particular versions.
Read more >Installing IPython — IPython 8.7.0 documentation
This document describes in detail the steps required to install IPython. ... IPython requires several dependencies to work correctly, it is not recommended...
Read more >5 Best Practices for Versioning Your Python Packages
Best Practice: Don't Deploy Prerelease Packages Prerelease segments let developers know if a Python package is still in development. Therefore, ...
Read more >7. Releasing and versioning - Python Packages
If your package has dependencies that are not on TestPyPI, you may need to tell pip to also search PyPI with the following...
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
As a workafound I prefered seting Ipython to < 8:
There is not good reason in sending black to production.
I didn’t not realised that this will be a problem, I’ll try to move it to optional dependency for next release.