We might then think about pinning jedi < 2.0.0 (which is probably years away). ✋ ⬇️ Thanks a lot! I guess the next release is going to be 1.0 anyway, so it shouldn't happen again. So not only you are impolite and haven't done your research, everybody see you incorrectly assume you know better than others and you've lost all credibility. You could have just asked in for a question "why are not you pinning to <0.19 starting with IPython 7.20", to which I would have responded. It's not because something seem obvious that it's correct.I'm one of the regular advocate to have version medata data and package content to be separated in conda/pypi for this exact reason.I spend month implementing on pushing the python_requires logic in pypi, and in pip to make sure when IPython dropped it did not break for Python 2 users.
#PIP INSTALL IPYTHON CANNOT FIND A VERSION INSTALL#
The fact that Ipython has not been pinning jedi means that any version of it released in the past that depends on jedi is at its merci to stop working as soon as a no backwards compatible change is introduced and used in Ipython.īy changing Ipython to make it jedi 0.18 compatible and releasing 7.20 you make that 7.20 operational today.
I am really disappointed that the maintainer of a great product as Ipython has such a limited knowledge about the problem.
0 kommentar(er)
