python-poetry / python-poetry/poetry-plugin-export
Option, no-binary
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 335
- Forks
- 57
- Avg merge
- 1h 23m
- Merged PRs (30d)
- 3
Description
Greetings.
As far as I can see, the export is not carrying the --no-binary option for selected packages.
For instance, we have a package wide configuration such as this
$ cat poetry.toml
[installer]
no-binary = ["confluent-kafka"]
And the no-binary is missing in the requirements.txt
$ cat requirements.txt
confluent-kafka==1.9.2 ; python_version >= "3.10" and python_version < "4.0"
--hash=sha256:24872e3e427b16f77461ae7e6cf48f9c5c03c06884ac51bad179580a4dd29145
[...]
-Settings under test
$ poetry self show plugins
• poetry-plugin-export (1.1.1) Poetry plugin to export the dependencies to various formats
1 application plugin
Dependencies
- poetry (>=1.2.0,<2.0.0)
- poetry-core (>=1.1.0,<2.0.0)
Thank you for the great job!
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
Reproduce the export using the shown poetry.toml configuration and inspect the generated requirements.txt. Check how the export handles the installer no-binary setting for confluent-kafka. Done means the exported requirement preserves the --no-binary option for selected packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100