Add ability to toggle dependency 'develop'

[Seanny123]

• 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.

Feature Request

Path-dependencies in Poetry can be optionally marked as 'develop' = True. However, there's no way to mark it as such via the poetry add command.

It would be nice to set the 'develop' = True when adding a path. For example:

poetry add ./my-package/ --develop

Or

poetry add ./my-package/ --editable

I think I can implement this myself if the core devs consider this feature to be beneficial.

[finswimmer]

Hello @Seanny123,

yes this is something really useful 👍

@abn listed this also in his suggestion in #3004.

fin swimmer

[abn]

I think this can happen independent of #3004. If this happens first, we just update the key it operates on when #3004 lands.

[0scarB]

@python-poetry/triage Hi, really like the project. Have used it for a couple of personal projects. Mind if I take on the issue

[finswimmer]

Hello @0scarB,

I don't know if @Seanny123 already started to work on it? Otherwise we really appreciate any contribution 👍

fin swimmer

[Seanny123]

Have no started yet. Go for it @0scarB

[0scarB]

@Seanny123 thx, I will :)

[0scarB]

Only directory and vcs dependencies support the develop attribute.

If we add develop = true without checking the source_type first then the follow unintuitive error message is raised for dependencies that do not support it

RuntimeError

  The Poetry configuration is invalid:
    - [dependencies.<dependency>] {'version': '<version>', 'develop': True} is not valid under any of the given schemas

It would be better to raise an explicit error such as The develop flag is not supported for dependencies of type <source_type>
Unfortunately I don't see an elegant way of doing this without changing how poetry-core dependencies handle the develop parameter.
Thoughts?

[finswimmer]

Hello @0scarB,

the error message poetry raises are in general very technical and it is not always obvious to the end-user, but are very useful for debugging. That's a general topic we can improve. I guess there was already somewhere a ticket about this 🤔 .

fin swimmer

[0scarB]

@finswimmer Thanks for the feedback, I totally agree. After working on #3004 I think that the dependency classes need to be refactored to have the json_schema as a single source of true, inheriting from superclasses/interfaces for common options such as optional, extras and editable/develop. I'll try and find the issue or create a new one and write up a more detailed proposal.

[finswimmer]

This is now possible in the current preview release 1.2.0a2 by:

-e, --editable           Add vcs/path dependencies as editable.

[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.