Issue #3575
Dev requirements installed outside of the pulp virtualenv
Description
The requirements defined in dev_requirements.txt are installed in the wrong place by the devel installer. Check pip freeze both within and without the virtualenv to see.
History
#1
Updated by CodeHeeler about 2 years ago
The packages effected are listed in dev_tools here as "useful":
https://github.com/pulp/devel/blob/3.0-dev/ansible/roles/dev_tools/tasks/main.yml#L19
Whereas in dev the only "extra-requirements" come from the various requirements.txt:
https://github.com/pulp/devel/blob/3.0-dev/ansible/roles/dev/tasks/main.yml#L90
It's unclear if ipython listed in devel/pulp/dev_requirements.txt would cover that, but if so, it seems this should already work:
#2
Updated by dalley about 2 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 36
#3
Updated by rchan about 2 years ago
- Sprint changed from Sprint 36 to Sprint 37
#4
Updated by rchan about 2 years ago
- Sprint changed from Sprint 37 to Sprint 38
#5
Updated by dalley almost 2 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dalley
#6
Updated by dalley almost 2 years ago
- Status changed from ASSIGNED to CLOSED - NOTABUG
ipython is depended on by one of the Fedora packages installed as part of the "dev_tools" role
https://github.com/pulp/devel/blob/master/ansible/roles/dev_tools/tasks/main.yml#L32
The dev_requirements.txt (etc.) files are all being installed inside the virtualenv as far as I can tell.
#7
Updated by daviddavis about 1 year ago
- Sprint/Milestone set to 3.0.0
#8
Updated by bmbouter about 1 year ago
- Tags deleted (
Pulp 3)
Please register to edit this issue
.