Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
PEP 517 implementation #5743
PEP 517 implementation #5743
Changes from 1 commit
744b8cf
de4d503
14f35f9
8fbf78d
4de2915
b9e92a7
b62284a
48e9cb6
ab3e216
a82b7ce
4281bf8
c8d8e37
c0ed438
41b07c9
9d2b178
f40491b
83979fe
f10be25
3c94d81
a4c7d7d
f805ac1
689f97c
817ef1a
4ca38e0
cf4d84e
e8f7aa1
3a0f9b1
6b7473d
85e4f8e
f06a0cb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Having played around a bit, perhaps we should use a different name here: pip-wheel-metadata stands out... Perhaps a
.
at the start and perhaps even a sub-folder.pip-metadata/wheel
would be a good idea?Idk. It's a little subjective but I expect this to be something that shows up in development constantly so we should try to optimize the ergonomics here.
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.
Perhaps
build/pip-wheel-metadata
?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 like how
build/pip-wheel-metadata
would look here.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.
Break this up into 2 separate functions that get called by this one?
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 think this can be simplified to:
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.
Or even better:
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'm OK with this - but don't really know the pkg_resources functions well enough to judge the impact. I'll wait for @pradyunsg to do his review, and then I'm happy to just replace the existing
get_dist
with this one.On the other hand, it would also be just as easy to put in what we have, and then follow up with a PR simplifying
get_dist
(in the interest of smaller more focused PRs being better). But as long as making the change doesn't trigger a new wave of weird CI failures, it doesn't really make much difference - this PR is already way too complicated, one more commit won't make much difference 😉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'm on board for making more follow up PRs for cleanups. This PR is already a little unwieldy in size and it's taken me a lot longer than I estimated to even try it out.
I've bumped existing notes just so that I don't have to scroll too high when taking a pass later to see what places we've already identified for improvements/refactors.