Skip to content

Don't use Python 3 stdlib stubs in Python 2 mode #10422

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

Merged
merged 1 commit into from
May 5, 2021
Merged

Conversation

JukkaL
Copy link
Collaborator

@JukkaL JukkaL commented May 5, 2021

Previously we could find stubs both in stdlib/@python2 and
stdlib for the same top-level package, which could result in a
mix of Python 2 and 3 stubs being used.

Now if we find stubs for a package in the @python2 directory, we
skip the parent directory.

Fixes #10421.

Previously we could find stubs both in `stdlib/@python2` and
`stdlib` for the same top-level package, which could result in a
mix of Python 2 and 3 stubs being used.

Now if we find stubs for a package in the `@python2` directory, we
skip the parent directory.

Fixes #10421.
@JukkaL JukkaL merged commit 4518b55 into master May 5, 2021
@JukkaL JukkaL deleted the py3-py2-stubs branch May 5, 2021 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Python 3 stdlib stubs are sometimes used in Python 2 mode
2 participants