Story #4711
As a user, I can specify Remote.includes with a requirements.txt
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Target Release - Python:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
This will fill out the common workflow:
1. pip install something from pypi. (pip will do dependency resolution)
2. pip freeze > requirements.txt (will include packages and all deps)
3. Create a warehouse remote, with requirements.txt used to populate the includes
This will significantly simplify the workflow, preventing the user from having to hand-parse their own includes.
Related issues
History
#1
Updated by amacdona@redhat.com almost 3 years ago
- Copied to Story #4713: As a user, I can specify Remote.includes with a pipenv.lock files added
#2
Updated by CodeHeeler over 2 years ago
- Sprint Candidate changed from No to Yes
#3
Updated by amacdona@redhat.com over 2 years ago
- Groomed changed from No to Yes
- Sprint set to Sprint 53
#4
Updated by amacdona@redhat.com over 2 years ago
- Sprint changed from Sprint 53 to Sprint 54
#5
Updated by ttereshc over 2 years ago
- Sprint changed from Sprint 54 to Sprint 55
#6
Updated by CodeHeeler over 2 years ago
- Sprint deleted (
Sprint 55)
#7
Updated by rchan over 2 years ago
- Sprint Candidate changed from Yes to No
Remove Sprint Candidate flag after Sprint 57 grooming.
#8
Updated by dalley over 1 year ago
- Related to Story #4690: Implement package locking / digest specification added
#9
Updated by gerrod 11 months ago
- Status changed from NEW to CLOSED - DUPLICATE
Migrated to GitHub Issues: https://github.com/pulp/pulp_python/issues/345
.