Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
add `develop` option for git dependencies
See original GitHub issue- 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
It would be nice to add develop option for git dependencies.
So it would work in the similar way as path dependencies.
Rationale
Currently there’s no way to specify that git dependencies should be installed in non-editable mode (develop=false). So all git dependencies are installed in develop / editable (pip -e ...) mode.
Now imagine a situation that you are e.g. installing the dependency from your private repository using a tag (always points to the same commit). In this case you don’t want that dependency to be installed in develop mode (the source directory is not going to change). You want to use install instead of develop.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@dazza-codes that’s what I think, too. the poetry-core already fixed it. However, when would it be merged with poetry? I think this is a quite big issue for some people like me who uses private git repo as a private python package registry.
@abn Thanks for pointing this out, I updated poetry to the latest preview version and the develop flag now works perfectly 😁