-
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
How do we specify paste entrypoints #1300
Comments
i wonder whether an |
For the record, there is a way to avoid the need for paste entry point with Pyramid: Pylons/pyramid#3270 (comment) But I agree that entry points are still a useful feature for various use cases, so general-purpose packaging tools should support them. |
I think this issue can be closed. Maybe a new issue could be opened for documentation improvements as |
That other issue seems to be about scripts (I didn’t re-read all messages) |
Hello @merwok , the issue tracker isn't the right place for a applications documentation. We need it in first place, to have an overview about what work needs to be done. Of course it contains a lot of knowledge by the time. But if this is in general interested it should be put on the help page/documentation itself. fin swimmer |
I wasn’t saying to keep this ticket open to serve as documentation, but that the ticket is a doc bug, i.e. a request to enhance poetry’s doc and avoid other people asking the same question in the future. |
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. |
Question
How can I replicate the non-script / paste entrypoints? Specifically, for a pyramid project, I've got:
Is there a way to do this in poetry?
The text was updated successfully, but these errors were encountered: