-
Notifications
You must be signed in to change notification settings - Fork 19
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
Replace packaging with packvers #108 #109
Conversation
a04b5f4
to
e7baa79
Compare
After analysing I found that due to that change in Packvers, we need to update our https://github.com/nexB/dparse2 for packvers and packaging change in the release and https://github.com/nexB/pip-requirements-parser to in the release , after that this PR will have all Test pass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you ++ !
"Packvers added" may not be the best name for this PR. What about "Replace packaging with packvers" instead?
Also on the commit message style, your use of things such as "packaging-to-packvers-done-in-resolution.py" may not be something we typically use... look for other commit messages for inspiration and also at https://aboutcode.readthedocs.io/en/latest/contributing/writing_good_commit_messages.html
See also the other review comments I posted for your kind consideration.
Okay sure will change accordingly : ) |
4196298
to
862f00b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you ... here are some review comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the updates. Do you mind to squash your commits in a single commit with a good commit message?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and ready to merge once squashed!
Done ✔️, can merge now :") |
@swastkk you did not squash it all in one commit, you still have 15 commits... you squash and force push. https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History |
e11872c
to
eae13cf
Compare
Is it okay now?? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Can you make one last change and amend your commit?
We want to subject to be using imperative style (e.g., Replace not Replaced) and to be subject line must be under 50 characters and ew extra things to review at https://aboutcode.readthedocs.io/en/latest/contributing/writing_good_commit_messages.html
eea5a58
to
1999fdc
Compare
Now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
"Replace packaging with packvers and bump packages version" is still at 57 chars... can you do something more or less like this instead:
Replace packaging library with packvers #108
Work around changes in packaging by replacing it with packvers
to avoid issues with missing packaging.version.LegacyVersion.
Also bump the versions of dparse2 and pip-requirements-parser
with new versions that are not subject the LegcacyVersion issue.
Adjust the code and tests accordingly.
Reference: https://github.com/nexB/python-inspector/issues/108
Reference: https://github.com/pypa/packaging/issues/530
Signed-off-by: swastik <[email protected]>
And please remove all changes you made that are not strictly about this... I am not sure what happened but you end up with unrelated changes. Do not hesitate to ask for help on the Gitter chat!
Thanks again for your preseverance.
53934bf
to
2a36d33
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update. One last nit before we can merge.
ea761e5
to
0bdaa36
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here are a few last nits.
* Work around changes in packaging by replacing it with packvers to avoid issues with missing packaging.version.LegacyVersion. * Also bump the versions of dparse2 and pip-requirements-parser with new versions that are not subject the LegcacyVersion issue. * Adjust the code and tests accordingly. Reference: aboutcode-org#108 Reference: pypa/packaging#530 Signed-off-by: swastik <[email protected]>
0bdaa36
to
6579412
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good .... Thank you ++
Packvers added in resolution.py and changed the version of pip-requirments-parser too.
for the aboutcode-org/scancode.io#576 and #108 issue as well.
Signed-off-by: Swastik Sharma [email protected]