-
Notifications
You must be signed in to change notification settings - Fork 151
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
Checking projects using Poetry >= 1.5.0 fails #479
Comments
@plaa, thanks for this report; in the coming month, we are releasing a 3.0 Safety version where this issue is addressed. |
Great! I just ran into this same error |
We have also run into this issue.. Fix would be much appreciated! |
Hi @plaa and everyone involved, Thank you for your patience and for bringing this issue to our attention. We're pleased to inform you that Safety version 3 has been released, and this version addresses the issue with parsing poetry.lock files for projects using Poetry 1.5.0 or newer. The update ensures compatibility by handling the changes in the poetry.lock file structure. Please update to Safety version 3 and test your environment. If you encounter any issues or have further questions, please let us know. Thank you for your continued support and for helping us improve Safety! Best Regards, |
Description
Safety uses dparse to parse the poetry.lock file. Poetry deprecated and in 1.5.0 removed writing of the
category
field into the poetry.lock file, while dparse assumes this field to always be present. Thus safety fails with the exceptionMalformed poetry lock file
for any project using Poetry 1.5.0 (released in May) or newer.dparse issue: pyupio/dparse#67
The text was updated successfully, but these errors were encountered: