FS#56396 - [python-jedi] python-parso dependency
Attached to Project:
Community Packages
Opened by null (null) - Tuesday, 21 November 2017, 12:34 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 26 November 2017, 20:03 GMT
Opened by null (null) - Tuesday, 21 November 2017, 12:34 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 26 November 2017, 20:03 GMT
|
Details
Description:
python-jedi depends on python-parso (PKGBUILD) and has parso==0.1.0 dependency in /usr/lib/python3.6/site-packages/jedi-0.11.0-py3.6.egg-info/requires.txt . But the current version of parso is 0.1.1 and i.e. aur/python-jedihttp-git failes due to this with the error: pkg_resources.DistributionNotFound: The 'parso==0.1.0' distribution was not found and is required by jedi Changing parso==0.1.0 to parso==0.1.1 seems to work great. Additional info: * python-jedi (0.11.0-1) * python-parso (0.1.1-1) Steps to reproduce: Install python-jedi, python-parso and python-jedihttp-git (aur) and do a jedihttp --help |
This task depends upon
Closed by Jelle van der Waa (jelly)
Sunday, 26 November 2017, 20:03 GMT
Reason for closing: Fixed
Additional comments about closing: python-jedi-0.11.0-2-any.pkg.tar.xz
Sunday, 26 November 2017, 20:03 GMT
Reason for closing: Fixed
Additional comments about closing: python-jedi-0.11.0-2-any.pkg.tar.xz
The real question is, why does jedi violate good setuptools practice by hardcoding an exact version number? Given that parso is created by the same author who goes around bragging on all his project READMEs about how he uses semantic versioning, there is absolutely no excuse for pinning versions.