Project

Profile

Help

Issue #3712

closed

pulp3 packages should not pin pulp dependencies

Added by bizhang over 6 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

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

Also available in: Atom PDF