GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||
GeezerVison is showing github.com — gh-108303: Move all XML-related test files to `test_xml` by sobolevn · Pull Request #114344 · python/cpython Conversation
|
|
Hum, I don't get the PR description. So, what it does: It changes also findfile() of test.support: if subdir is not a string, use What do you think about removing |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I do not think that it is worth to do. Unlike to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@serhiy-storchaka sorry, I don't agree. They might have any implementation details, but they are still sharing the same namespace and they use the same fixture files. It is logical for test to have the same namespaces as regular code does. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
af1b057 to
13fdbc7
Compare
|
@vstinner I tried to remove |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I suggest to close this issue.
There are different aspects:
test_xml.test_test_minidom. Yes, it's possible.test_xml into sub-tests to run them in parallel.xml.minidom implementation has nothing to do with xml.etree.they are still sharing the same namespace and they use the same fixture files. It is logical for test to have the same namespaces as regular code does.
We have many "os-like" and "socket-like" tests in separated tests, and that's why we have helpers such as support.os_helper and support.socket_helper. I don't buy the argument "putting everything at the same place is better".
While it's very tempting to put "everything related to XML" in a test package, for this change, I prefer to stick to the status quo: "flat namespace is better than nested" (PEP 20) :-)
Not changing tests keeps the Git history linear (no custom command line option needed) and avoids developers to change their habits. I don't think that the benefits are way higher than drawbacks (moving code).
Test files are already in the xmltestdata directory.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Ok, sounds convincing 👍 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.