-
Notifications
You must be signed in to change notification settings - Fork 52
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
1.6.0: Error installing develop
packages from pyproject.toml
#244
Comments
Does it work if you run I can't yet follow why this is specific to |
Unfortunately it fails too:
The 1.5.0 version would return:
|
this looks completely different from what you first reported. Here it seems as though the new json validation is stricter than the old, I think it is unhappy becuase the I suppose the schema was always wrong to require this. Or maybe the fastjsonschema validation is wrong, I'm not sure. Edit: the first of these I reckon. There's no scheme at the front of this string, it's not a URI. |
@dimbleby that was it! Thank you! Do you know why this error showed up just today? Is it safe to assume this is related to https://github.com/python-poetry/poetry-core/releases/tag/1.8.0 relase? So for anyone looking for a resolution - If you are using |
Yes, it is. We switched from |
Issue
After updating poetry-plugin-export to version 1.6.0, we began encountering errors when attempting to pip install packages generated with the export command. This happens specifically for packages added to pyproject.toml with
develop = true
attribute. The export command creates arequirements.txt
entry with pinned commit hash, while pip install tries to install from themain
branch as specified inpyproject.toml
.Could we adjust the behavior for packages with
develop = true
inpyproject.toml
to utilize thereference
(e.g., "main") over theresolved_reference
(specific commit hash) for their dependecies when creating therequirements.txt
?Error
Pip install command is failing with the following error:
Configuration
The package is added in develop mode in pyproject.toml.
The glue-schema-registry dependecy is defined inside the customer-kafka, with the following entry in pyproject.toml.
and the poetry.lock:
The text was updated successfully, but these errors were encountered: