Issue #3712
closed
pulp3 packages should not pin pulp dependencies
Description
Currently we are pinning the pulpcore and pulpcore-common dependencies.
E.g. pulpcore-plugin has its pulpcore dependency pinned to pulpcore==3.0.0b3 [0]
This introduces problems when we are doing a dev install. The packages are not lockstepped
so when pulpcore is updated to 3.0.0b4 the dev install overrides the editable install of pulpcore with the 3.0.0b3 version on PyPI.
When GA is released we can pin dependencies with ~=, but unfortunately this is not possible for beta releases.
I think if plugins do not want to risk breakage they should for now, pin both the pulpcore-plugin and pulpcore version in the individual plugin, and we should get rid of the pinned pulp dependencies in pulpcore, and pulpcore-plugin for now.
[0] https://github.com/pulp/pulp/blob/3.0-dev/plugin/setup.py#L4
Updated by dalley over 6 years ago
- Status changed from NEW to POST
- Assignee set to dalley
Added by dalley over 6 years ago
Added by dalley over 6 years ago
Revision 21ad8fe7 | View on GitHub
Fix dependencies for source installation
pulpcore is currently at 3.0.0b4, pulpcore-plugin requires 3.0.0b3, so the editable installation fails and it falls back to installing from PyPI. So the developer installation will not actually be a developer installation.
Updated by dalley over 6 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp|21ad8fe7ccf9f5d2f8bd3cf30bf18daac694ddc5.
Updated by bmbouter about 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Fix dependencies for source installation
pulpcore is currently at 3.0.0b4, pulpcore-plugin requires 3.0.0b3, so the editable installation fails and it falls back to installing from PyPI. So the developer installation will not actually be a developer installation.
closes #3712 https://pulp.plan.io/issues/3712