-
-
Notifications
You must be signed in to change notification settings - Fork 32k
bpo-35181: Correct importlib documentation for some module attributes #15190
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
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.
Thanks for the PR. The title should be changed to something a bit more descriptive so that the core devs know which top-level module it involves without having to look at the PR itself. I would advise something along the lines of "Update importlib documentation for module attributes".
I have a few suggestions:
@aeros167 Thank you for the suggestions. I have updated the PR title. As for your other suggestions, I am fine with them but I would like to have @ericsnowcurrently's opinion before applying them. |
Since this PR is involving documentation corrections and does not add any new sections, I'll add a |
@ericsnowcurrently What do you think of @aeros167 suggested changes? |
Co-authored-by: Kyle Stanley <[email protected]>
Co-authored-by: Kyle Stanley <[email protected]>
See comments in place above. Thank you for the requested changes, but I think this PR is good now. Using Dismiss review was the only way I could see to avoid this blocking the PR.
@maggyero: Status check is done, and it's a failure ❌ . |
I'll check out this branch locally and repair the build failures. |
@maggyero: Status check is done, and it's a success ✅ . |
Sorry, I can't merge this PR. Reason: |
@maggyero: Status check is done, and it's a success ✅ . |
1 similar comment
@maggyero: Status check is done, and it's a success ✅ . |
Sorry, I can't merge this PR. Reason: |
1 similar comment
Sorry, I can't merge this PR. Reason: |
@maggyero: Status check is done, and it's a failure ❌ . |
@maggyero: Status check is done, and it's a success ✅ . |
Thanks @maggyero for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9. |
…pythonGH-15190) @ericsnowcurrently This PR will change the following: In the library documentation importlib.rst: - `module.__package__` can be `module.__name__` for packages; - `spec.parent` can be `spec.__name__` for packages; - `spec.loader` is not `None` for namespaces packages. In the language documentation import.rst: - `spec.loader` is not `None` for namespace packages. Automerge-Triggered-By: GH:warsaw (cherry picked from commit 27f1bd8) Co-authored-by: Géry Ogam <[email protected]>
GH-22872 is a backport of this pull request to the 3.9 branch. |
…pythonGH-15190) @ericsnowcurrently This PR will change the following: In the library documentation importlib.rst: - `module.__package__` can be `module.__name__` for packages; - `spec.parent` can be `spec.__name__` for packages; - `spec.loader` is not `None` for namespaces packages. In the language documentation import.rst: - `spec.loader` is not `None` for namespace packages. Automerge-Triggered-By: GH:warsaw (cherry picked from commit 27f1bd8) Co-authored-by: Géry Ogam <[email protected]>
GH-22873 is a backport of this pull request to the 3.8 branch. |
…GH-15190) @ericsnowcurrently This PR will change the following: In the library documentation importlib.rst: - `module.__package__` can be `module.__name__` for packages; - `spec.parent` can be `spec.__name__` for packages; - `spec.loader` is not `None` for namespaces packages. In the language documentation import.rst: - `spec.loader` is not `None` for namespace packages. Automerge-Triggered-By: GH:warsaw (cherry picked from commit 27f1bd8) Co-authored-by: Géry Ogam <[email protected]>
…GH-15190) @ericsnowcurrently This PR will change the following: In the library documentation importlib.rst: - `module.__package__` can be `module.__name__` for packages; - `spec.parent` can be `spec.__name__` for packages; - `spec.loader` is not `None` for namespaces packages. In the language documentation import.rst: - `spec.loader` is not `None` for namespace packages. Automerge-Triggered-By: GH:warsaw (cherry picked from commit 27f1bd8) Co-authored-by: Géry Ogam <[email protected]>
…pythonGH-15190) @ericsnowcurrently This PR will change the following: In the library documentation importlib.rst: - `module.__package__` can be `module.__name__` for packages; - `spec.parent` can be `spec.__name__` for packages; - `spec.loader` is not `None` for namespaces packages. In the language documentation import.rst: - `spec.loader` is not `None` for namespace packages. Automerge-Triggered-By: GH:warsaw
@ericsnowcurrently This PR will change the following:
In the library documentation importlib.rst:
module.__package__
can bemodule.__name__
for packages;spec.parent
can bespec.__name__
for packages;spec.loader
is notNone
for namespaces packages.In the language documentation import.rst:
spec.loader
is notNone
for namespace packages.https://bugs.python.org/issue35181
Automerge-Triggered-By: GH:warsaw