python-poetry / python-poetry/poetry-plugin-export
Idea: add support for lock packages
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 335
- Forks
- 57
- Avg merge
- 1h 23m
- Merged PRs (30d)
- 3
Description
I'm currenlty exporting requirements in a package using a script based on poetry and the lock information.
I think this plugin would be a good place to add that functionality using --format wheel to create a package which depends on all lock versions. Often I get asked why not just use requirements.txt: python packages are more easily distributed though existing channels and my use-case requires me to ignore (not pin down) some parts of the depenency tree.
As this is the official export plugin, I would love to help integrate the logic from poetry-lock-packge into this plugin.
My current plugin implementation can be tracked here: https://github.com/bneijt/poetry-lock-package/pull/13
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the export plugin's existing command and the linked poetry-lock-package pull request, focusing on how --format wheel should use lock information. Done means the scope and behavior for preserving locked versions while leaving selected dependency-tree parts unpinned are agreed and integrated into this plugin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100