python-poetry / python-poetry/poetry-plugin-export
Providing both `--with Foo` and `--without Foo` results in ignoring `--without`
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 335
- Forks
- 57
- Avg merge
- 1h 23m
- Merged PRs (30d)
- 3
Description
Currently providing --with and --without simultaneously results in without being ignored.
[tool.poetry]
name = "aaa"
version = "0.1.0"
description = ""
authors = ["pmav99 <pmav99@mail.com>"]
readme = "README.md"
[tool.poetry.dependencies]
python = "^3.9"
[tool.poetry.group.optional]
optional = true
[tool.poetry.group.optional.dependencies]
pytest= "*"
[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"
$ poetry export --without-hashes --without optional | ag pytest
$ poetry export --without-hashes --with optional | ag pytest
pytest==6.2.5; python_version >= "3.6"
$ poetry export --without-hashes --with optional --without optional | ag pytest # <- Without is being ignored
pytest==6.2.5; python_version >= "3.6"
I think that throwing an Error in this case is probably a better idea.
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 reproducing the documented poetry export commands with --with optional and --without optional, then trace where these options are handled. Done means the conflicting combination no longer silently ignores --without, with behavior matching the decided resolution, such as reporting an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100