-
Notifications
You must be signed in to change notification settings - Fork 3
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
Experimental lock file integration fails with certain dependencies #45
Comments
Related to #24 |
Thanks for the report. On the first impression, my gut feeling is to say that the issue is related to the |
Thanks, that was my first guess as well, and so I wanted to report it for you to see. Thanks for this awesome plugin by the way. I really like |
Aside (unrelated to the issue): Maybe it is of no consequence (or at least not for your use cases), but I am a bit surprised to see the following in your
1. Does it mean that you run tox with a command like the following?
2. Do you know about tox's
|
I will push and release a change so that URL dependencies in the lockfile are handled. But it is clear that there is much more that is missing: git dependencies and path dependencies, as well as Python restricted dependencies, and so on. But I would add those only if someone raises a need for them. I am reluctant to add such code, since my hope is that it can be entirely delegated to poetry-core if and when the following change is published: |
Fix released in version 0.0.5. Let me know if it works, feel free to reopen the issue if it does not. |
I actually saw that after I posted this issue. I didn't know that was a feature of
I agree this is a bit weird. The reason for this is to make it really easy for developers to get a locked version of |
Awesome, I will test tomorrow and let you know. |
pyproject.toml:
tox.ini
Output:
poetry.lock
The text was updated successfully, but these errors were encountered: