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
Move test_namespace_pkgs into test_importlib. #65296
Comments
While working on bpo-19711 it dawned on me that test_namespace_pkgs might be more appropriate as a submodule of test_importlib. The feature doesn't have it's own module nor is it otherwise independent of importlib. I don't want to introduce churn here for the sake of conceptual purity. Rather, the module would be more discoverable if associated with importlib in this way. For bpo-19711 I wrote a test case that was overly complicated and did not work (goes hand-in-hand, no?) that I would not have spent time on if I'd remembered about test_namespace_pkgs or seen it somewhere under test_import*. As a bonus, this change moves 1 file and 1 directory out of Lib/test (a directory that takes "flat is better than nested" to the extreme). Any objections? |
Fine by me. |
Makes sense to me. |
New changeset 6d44bd8066ee by Eric Snow in branch 'default': |
New changeset 48790b202a50 by Eric Snow in branch '3.4': |
I seriously need to remember to apply to 3.4 and merge forward! :P |
New changeset 99265d30fa38 by Ned Deily in branch '3.4': New changeset 7aae2b9fcfad by Ned Deily in branch 'default': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: