bpo-43312: Functions returning default and preferred sysconfig schemes#24644
bpo-43312: Functions returning default and preferred sysconfig schemes#24644pfmoore merged 6 commits into
Conversation
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
acadc40 to
a0d613f
Compare
March 29, 2021 20:17
|
Uh, how do I remove the stale label? |
Sorry, something went wrong.
pfmoore
left a comment
There was a problem hiding this comment.
I can't say whether the choices in _get_preferred_schemes are correct, but they seem reasonable. Unless there's anything we can check them against, I'd say we should go with them.
Sorry, something went wrong.
hroncok
left a comment
There was a problem hiding this comment.
I ❤️ it!
Several non-blocking questions attached.
However, I have a very strong suggestion: Please add tests.
Sorry, something went wrong.
This reduces logic duplication with a slight performance tradeoff.
|
I’ve changed |
Sorry, something went wrong.
|
The implementation looks good to me. |
Sorry, something went wrong.
|
I’m wondering whether we should add documentation for the private |
Sorry, something went wrong.
At least a docstring would be great, yes. |
Sorry, something went wrong.
|
Documentation entry added 👍 Edit: Plus converting %-formatting to f-strings. |
Sorry, something went wrong.
Drive-by refactoring.
|
Curiosity question: Should distutils use this? |
Sorry, something went wrong.
|
Ideally yes, but distutils’s implementation around this is structured very differently, and tangled with a lot of things inside |
Sorry, something went wrong.
zooba
left a comment
There was a problem hiding this comment.
Would like to see that error message improved, but the rest seems fine to me. I'm just taking on trust that it's sufficient for distros to override what they need, because I don't know that side of it well enough.
Sorry, something went wrong.
|
Another nudge 🙂 |
Sorry, something went wrong.
|
I believe all comments have been addressed, and I see no remaining concerns raised and general approval of the change, so I'm going to merge this based on my approval above. |
Sorry, something went wrong.
https://bugs.python.org/issue43312