Skip to content

/ peps

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

Jump to bottom

PEP 561: Clarify ordering of module resolution #807

Merged
merged 1 commit into from Oct 12, 2018
Merged

PEP 561: Clarify ordering of module resolution #807

merged 1 commit into from Oct 12, 2018

Conversation

@ethanhs
Copy link
Contributor

@ethanhs ethanhs commented Oct 12, 2018

As brought up in python/mypy#5520.

cc @gvanrossum
@ethanhs
Clarify ordering of PEP 561 module resolution
Verified
This commit was signed with a verified signature.
ethanhs Ethan Smith
GPG key ID: 684B1F8C4560E284 Learn about signing commits
Loading status checks…
84f6dbf
@gvanrossum gvanrossum merged commit c509ce2 into python:master Oct 12, 2018
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@ethanhs ethanhs deleted the ethanhs:orderpep561 branch Oct 12, 2018
@sproshev
Copy link

@sproshev sproshev commented Nov 30, 2018

@ethanhs If package is distributed with stubs (e.g. attr: __init__.py and __init__.pyi), what category should be used from Module Resolution Order for it?
@gvanrossum
Copy link
Member

@gvanrossum gvanrossum commented Nov 30, 2018

For any .py file, including __init__.py, if there is a corresponding .pyi file in the same directory, that .pyi is used exclusively.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
CLA signed
Projects
None yet
Milestone
No milestone
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
@ethanhs @sproshev @gvanrossum @the-knights-who-say-ni