We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--dev
The deprecated --dev option does not work as intended: when running with --dev, the dev dependencies are not being exported.
Running poetry export with or without the --dev option won't make a difference:
poetry export --dev --format=requirements.txt --output=requirements-dev.txt poetry export --format=requirements.txt --output=requirements.txt diff requirements.txt # no output
pyproject.toml
poetry export --dev --format --requirements.txt --output=requirements-dev.txt
[project] name = "poetry-demo" version = "0.1.0" requires-python = ">=3.10" dependencies = [ ] [build-system] requires = ["poetry-core>=2.0.0,<3.0.0"] build-backend = "poetry.core.masonry.api" [tool.poetry.group.dev.dependencies] pytest = "^8.3.4" [tool.poetry.requires-plugins] poetry-plugin-export = ">=1.9"
I know that the dev dependencies can be easily exported with the --with=dev option, however the --dev, although deprecated, should still work.
--with=dev
Poetry version: 2.0.1 poetry-plugin-export version: 1.9.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The deprecated
--dev
option does not work as intended: when running with--dev
, the dev dependencies are not being exported.Running poetry export with or without the
--dev
option won't make a difference:Steps to reproduce:
pyproject.toml
file with dev dependenciespoetry export --dev --format --requirements.txt --output=requirements-dev.txt
Example pyproject.toml
I know that the dev dependencies can be easily exported with the
--with=dev
option, however the--dev
, although deprecated, should still work.Poetry version: 2.0.1
poetry-plugin-export version: 1.9.0
The text was updated successfully, but these errors were encountered: