python-poetry / python-poetry/poetry
Ignore "develop = true"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 2.5k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 30
Description
Issue Kind
Brand new capability
Description
I know this issue came up here several times but I couldn't find a good solution for that.
Let's say I'm using the following dependency:
[tool.poetry.dependencies]
my_lib = {path = "../../my_lib", develop = true}
when I deploy to production I want it to run without develop = true but it doesn't seems there is an option to do so.
I don't want to split it into another group because this will mean duplicating all my dependencies (which I develop locally) and this does not make any sense.
Shouldn't there be some --production flag to solve this problem?
Impact
Currently, I need to workaround or duplicate 19 dependencies.
Workarounds
A script that changes the develop = true to false on the deployment pipeline.
Contributor guide
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 tracing how Poetry handles path dependencies with develop = true and how production installation options are represented. Define the expected behavior for the provided dependency example, then add or update coverage for a production-mode invocation that avoids editable installation without duplicating dependency groups.
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
- Mostly clear
- Newbie friendliness
- 35/100