-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
gh-108303: Move config parser data to Lib/test/configparserdata/
#111879
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
Conversation
…a/` (pythongh-111879) (cherry picked from commit cc18b88) Co-authored-by: Nikita Sobolev <[email protected]>
…a/` (pythongh-111879) (cherry picked from commit cc18b88) Co-authored-by: Nikita Sobolev <[email protected]>
GH-111882 is a backport of this pull request to the 3.12 branch. |
GH-111883 is a backport of this pull request to the 3.11 branch. |
|
Failures look related |
They are indeed related because looks like the data files don't get installed. |
Fixing |
Ooooh, right. It's good that we have buildbots to test that :-) |
Better would be to fail faster (#81224). This change is also implicated In jaraco/configparser#70. It's probably good to learn that the backport was inadvertently depending on fixtures in the Python test suite. Additionally, it's an indication that this change has implications for the backport's test suite and it would be good for me to get notified when there are such changes. I think what that means is that I just need to add my username to the codeowners for the relevant paths. |
There are two options:
idlelib
)test_configparser
package with these files andtest_configparser.py
(it is more complex to add, since requires several build-step changes, while in my opinion does not add much)What do others think?