You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[x ] I have searched the issues of this repo and believe that this is not a duplicate.
[x ] I have searched the documentation and believe that my question is not covered.
Feature Request
Various projects I am working on requires separation of code into multiple different modules (and hence repositories). I can do this with pip via pip install -e git+https://.../my-module.git and it saves it into src/my-module in editable mode.
This is important during development because you can work on both code bases at the same time such as updating the logic in my-module while running integration tests in your main project.
This pattern is commonly used in PHP's composer with the --preferred-source flag (which is equivalent to editable mode). The package will be checked out as a git repo inside the vendor directory where you can make any necessary modifications etc independently of the main project.
I've been looking through the code and I can't seem to find a way to do this with poetry 1.0.5. Currently it does a git checkout into the venv's src/my-module as a headless commit. Alternatively, you can add with a path, but that requires 2 packages sitting side by side, which is not always the case for various development setup.
I was hoping #755 would solve this issue, but it addresses a different problem altogether.
The text was updated successfully, but these errors were encountered:
Feature Request
Various projects I am working on requires separation of code into multiple different modules (and hence repositories). I can do this with pip via
pip install -e git+https://.../my-module.git
and it saves it into src/my-module in editable mode.https://github.com/boto/boto3/blob/develop/requirements.txt is an example I found that has this pattern, where botocore got imported into boto inside src/.
This is important during development because you can work on both code bases at the same time such as updating the logic in
my-module
while running integration tests in your main project.This pattern is commonly used in PHP's composer with the
--preferred-source
flag (which is equivalent to editable mode). The package will be checked out as a git repo inside the vendor directory where you can make any necessary modifications etc independently of the main project.I've been looking through the code and I can't seem to find a way to do this with poetry 1.0.5. Currently it does a git checkout into the venv's src/my-module as a headless commit. Alternatively, you can add with a path, but that requires 2 packages sitting side by side, which is not always the case for various development setup.
I was hoping #755 would solve this issue, but it addresses a different problem altogether.
The text was updated successfully, but these errors were encountered: