Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1817967
Summary: | python-pip-shims fails to build with pip 20.0.x: 'NoneType' object is not callable | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
Component: | python-pip-shims | Assignee: | Lumír Balhar <lbalhar> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | cstratak, lbalhar, mhroncok, mplch |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 06:33:15 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1803234, 1785415 |
Description
Miro Hrončok
2020-03-27 10:52:58 UTC
The problem seems to be caused by incompatibilities between shims 0.3.2 and the latest pip we have in rawhide (20.0.2). Shims 0.3.2 works with pip 19.3.1 but not with 20.0.2. As Miro pointed out in the PR, we cannot update shims because it might break pipenv. But, how to solve this? We can let pipenv use bundled shims and update this package. Any other possibility? If we use bundled shims, we can as well retire this. The only reason we have this package is pipenv. I think we have several options: - rebundle + retire - figure out when the new release of pipenv happens (that uses the new release of shims) - backport the fixer Oh, this fails to build with new pip (and not with Python3.9 per se), we can skip the test explaining the reasons. We have done that in the past. https://koschei.fedoraproject.org/package/python-pip-shims We discussed it with Patrik and we think that retiring and bundling the shims back to the pipenv is the way to go. Pip-shims depends on pip heavily and if we cannot update it together with pip in Fedora, we should keep the older version bundled with the compatible pip in pipenv. It seems that pipenv might have a new release in foreseeable future and this release might happen also to bundled libraries but this situation will repeat either sooner or later. Patrik will try to bundle pip-shims back to pipenv and test it with the bundled version and we can then proceed with this change in rawhide. I suggest we wait with the retirement, see https://github.com/pypa/pipenv/pull/4169 -- new pipenv release is probably coming soon. Okay. It wasn't clear that the update of vendored dependencies happens in the next release. pip-shims is required only by pipenv and will be re-bundled back during the update of pipenv so this package can and will be retired then. This comment is mass posted to all bugs blocking the Python 3.9 tracker, sorry if it is not 100 % relevant. When in doubt, please ask. The Python 3.9 rebuild is in progress in a Koji side tag. If you fix this bug, please don't rebuild the package in regular rawhide, but do it in the side tag with: $ fedpkg build --target=f33-python The rebuild is progressing slowly and it is possible this package won't have all the required build dependencies yet. If that's the case, please just leave the fix committed and pushed and we will eventually rebuild it for you. You are not asked to go and try rebuild all the missing dependencies yourself. If you know there is a bootstrap loop in the dependencies, let me know and we can untangle it together. If you want to test your fix or reproduce the failure, you can still use the Copr repo mentioned in the initial comment of this bug: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/ Can we rebuild this without tests for now, before we update pipenv and/or debundle this in pipenv? It blocks the Python 3.9 rebuild of pipenv. Yes, sure, should I disable the tests in master branch? Yes please. Once done, build in --target=f33-python. Python 3.9 update: The f33-python side tag is currently being merged. New builds in f33-python are no longer possible, but python3 is not yet updated to Python 3.9 in rawhide. You can check when Python is Python 3.9 with: $ koji wait-repo f33-build --build python3.9-3.9.0~b1-3.fc3 And build the packages normally after that. This package is retired in rawhide. |