PipConsole safely avoid ctypes features from rich #13686
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Dec 8, 2025
Member
|
This looks like it’s working around a problem in Rich, and ideally should be fixed in Rich. Is there an upstream issue on this? |
1 task
Author
|
Thank you! I opened issue #13687, and linked patch for rich there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Note: I will add an issue and news entry soon.
Modify PipConsole so that it doesn’t use the
richfeatures that require ctypes when running in environments where ctypes is unavailable.This helps ensure that pip works properly on Python implementations that do not provide ctypes.
Please tell me if patching rich will be a better idea.