-
Notifications
You must be signed in to change notification settings - Fork 251
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
Optionally use resolved references in to_pep_508 #603
Conversation
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.
I have to say I was not thrilled about the change but since I don't see a better solution than adding a new parameter and this (finally) will solve a valid bug in the export plugin, let's go.
I have no idea how to update the documentation since by inspecting this library I found no documentation for any of the internal python functions.
It's just a reminder to think about it. There is nothing to update here.
Co-authored-by: Randy Döring <30527984+radoering@users.noreply.github.com>
Kudos, SonarCloud Quality Gate passed! |
Related-to: python-poetry/poetry-plugin-export#35
Well this pull request doesn't actually solve the issue linked above. But it is necessary to be able to solve it.
I've modified the
to_pep_508
function to return resolved references if called with the optional argumentresolved=True
. The default of this argument isFalse
in order to not make any backward incompatible changes that might adversely affect other code also making use of theto_pep_508
function.I have no idea how to update the documentation since by inspecting this library I found no documentation for any of the internal python functions.