Replace requirements.txt with Pipenv #56680
Labels
No Label
legacy project
Infrastructure: Websites
legacy project
Pillar
legacy project
Pillar Framework
legacy project
Pillar Website
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Resolved
Type::Bug
Type::Design
Type::Patch
Type::Report
Type::To Do
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/pillar#56680
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In short: we want to get rid of
requirements.txt
files in favour of using Pipenv.If we want to keep the inter-linking approach we have now, we'll need some extension to Pipenv. I've opened up a ticket on their Gitlab to discuss this.
Alternatively, we could rethink our strategy and rework Pillar and its extensions more into proper Python packages, and install them as such. This might require us to run our own Pypi-like service, which is totally possible.
Something we can't tackle on very short notice, so let's discuss the details here so we remember them later.
Added subscribers: @dr.sybren, @fsiddi