-
Notifications
You must be signed in to change notification settings - Fork 369
Fix rex parent_environ case sensitivity on Windows #2098
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
Open
thc1006
wants to merge
5
commits into
AcademySoftwareFoundation:main
Choose a base branch
from
thc1006:fix/rex-windows-parent-environ-case-2089
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
fa436d7
Fix rex parent_environ case sensitivity on Windows
thc1006 1c60859
Address review feedback for parent_environ case-insensitivity
thc1006 c0b42f8
Scope the case-insensitivity wording to parent_environ
thc1006 1c3299e
Fix env-shadowing in Windows test; add passthrough + mocked coverage
thc1006 c84ef86
sphinx stuff
JeanChristopheMorinPerso File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
Oops, something went wrong.
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.
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.
?
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.
tl;dr: happy to take the
Mapping[str, str]change, but it should usetyping.Mappingto stay 3.8-safe. Separately, the failing Ruff check looks like a pre-existing issue onmain, not something in this PR.On the base class:
Mappinghere is imported fromcollections.abc, and using one of those as a subscripted base (class X(Mapping[str, str])) only works on Python 3.9+. On 3.8 it raisesTypeErrorat import, and we still support 3.8 (python_requires >= 3.8). The other parametrized bases in the repo, likeAttrDictWrapper(MutableMapping[str, Any])andPackageOrderList(List[...]), go throughtypingfor that reason. I can switch this tofrom typing import Mappingand applyMapping[str, str], or leave it bare, whichever you prefer.On the Ruff failure: it's
ISC004atsrc/rez/utils/platform_.py:524(the PowerShell command list), which this branch doesn't touch. It reproduces on a cleanmain(4946f9de) with ruff 0.16.0, the newest release matching>= 0.15.0thatruff-actionpulls in. So it reads as the new ISC004 rule catching an existing line rather than anything from here. I'm happy to fold the one-line fix into this PR if that unblocks things, otherwise it may fit better as its own change onmain.Thanks for the sphinx pass too, the
:data:/:class:refs read a lot cleaner.