Installing CLI with setuptools style "scripts" vs "console_scripts".

[grabear]

• I have searched the issues of this repo and believe that this is not a duplicate.
  This is definitely a duplicate, but the Feature Request is different.
• I have searched the documentation and believe that my question is not covered.

Feature Request

It would be nice to install files as command line scripts vs installing modules as command line console_scripts.

The current ability of poetry to include "scripts" seems slightly misleading according to the setuptools documentation. I could be wrong, but it seems like the [tools.poetry.scripts] toml keyword should read more like [tools.poetry.console_scripts] or [tools.poetry.entry_points].

So I would like to request some clarity around this terminology in the documentation, as well as the implementation of setuptools style scripts.

I believe #241 (comment) addresses this as well. An associated PR is also open in #304

cc: @ojii

Thanks to any contributors to this project. It's an amazing tools that I'm excited to continue using.

Cheers,
@grabear

[grabear]

It's also not super clear in the documentation what the difference is between 'plugins' and 'scripts'.
Based on the original comment:

• poetry's scripts == setuptools' entrypoint/console_script
• setuptools' scripts keyword != poetry (is not represented by poetry)

And new information:

• poetry's plugins == setuptools' entrypoint/dynamic-discovery-of-services-and-plugins

By changing the link in the 'plugins' documentation to the one supplied above, I think that would also help clear things up:

From this (main page of setuptools) to this (the actual article).

[ojii]

I could bring my PR up to date if there is a consensus on the config syntax and if this is something that poetry wants to support. I've stopped working on it because the discussion in the original ticket got way out of scope so I lost interest and found other workarounds to solve my use case.

[tedmiston]

I agree the Poetry docs would benefit from clarity around these topics. My confusion was similar to @grabear until ending up on a few issues like this.

[funkyfuture]

yeah, it seems that a good load of topic-related issues opened here stem from that semantic twist.

[grabear]

@tedmiston @funkyfuture I'm glad I'm not the only one that was confused. I still have to come back to this issue sometimes to refresh my understanding of it all. @sdispater are there any developments surrounding this issue as well as related issues? #241 (comment) and #304

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[grabear]

This is definitely not a stale issue..

[geckon]

For the record check #1504

[finswimmer]

I think this is solved by python-poetry/poetry-core#40

[github-actions]

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.