Skip to content
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

Closed
2 tasks done
viraptor opened this issue Aug 14, 2019 · 9 comments
Closed
2 tasks done

How do we specify paste entrypoints #1300

viraptor opened this issue Aug 14, 2019 · 9 comments

Comments

@viraptor
Copy link

viraptor commented Aug 14, 2019

  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have searched the documentation and believe that my question is not covered.

Question

How can I replicate the non-script / paste entrypoints? Specifically, for a pyramid project, I've got:

    entry_points={
        'paste.app_factory': [
            'main = someproject:main',
        ],

Is there a way to do this in poetry?

@viraptor viraptor changed the title How do we specify paste endpoints How do we specify paste entrypoints Aug 14, 2019
@abn
Copy link
Member

abn commented Aug 18, 2019

@viraptor this is done via the plugin section.

[tool.poetry.plugins."paste.app_factory"]
main = "someproject:main"

@kasteph kasteph removed the question label Sep 23, 2019
@funkyfuture
Copy link
Contributor

i wonder whether an entrypoints section in the docs for the pyproject.toml that points to the plugins and scripts sections would be helpful to avoid such confusions. i'm always looking for it in the sidebar, but have to search the whole page to find what i'm looking for.

@merwok
Copy link

merwok commented Nov 8, 2019

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.

@pawamoy
Copy link

pawamoy commented Nov 28, 2019

I think this issue can be closed. Maybe a new issue could be opened for documentation improvements as scripts versus entrypoints versus plugins seems to create a lot of confusion.

@finswimmer
Copy link
Member

Hello all,

there is already a discussion about scripts/entrypoints in #241 and #1504.

I see it like @pawamoy that this issue can be closed in favor of the others.

If someone disagree please let me know :)

fin swimmer

@merwok
Copy link

merwok commented Dec 2, 2019

That other issue seems to be about scripts (I didn’t re-read all messages)
This one here was a question about entry point (which got answered, support is already there), so why not keep it open as a documentation ticket?

@finswimmer
Copy link
Member

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

@merwok
Copy link

merwok commented Dec 2, 2019

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.

Copy link

github-actions bot commented Mar 3, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants