-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
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
Single-file or env-only packages not allowed? #8292
Comments
You don't need to put anything special in the packages section of pyproject.toml, this Just Works. Please close. |
Can you give an example of it just working, because it doesn't for me. |
Just remove |
My apologies, seems like it's indeed looking for all three of That being said, a way to omitt the project name and version (without poetry defaulting to anything) would sure be nice. Just to prevent accidentally packaging/pypi-uploading something that is not intended to be shared in that way. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Don't actually know if it's a bug, nothing at all (because already implemented) or a feature; request.
Assuming my project to be packaged is a single file next to
pyproject.toml
in the file system hierarchy (i.e. in the same directory aspyproject.toml
).can I get poetry to accept that? I.e. what does the
package
attribute have to look like?Related: what if I just wanted to use poetry for the dependency pinning functionality, i.e. just to distribute a reliably reproducible virtual environment? Does that work? If not, consider this a issue a feature request.
The text was updated successfully, but these errors were encountered: