Skip to content
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

Unclear why --namespace-packages isn't enabled by default #6161

Closed
russelldavis opened this issue Jan 8, 2019 · 4 comments
Closed

Unclear why --namespace-packages isn't enabled by default #6161

russelldavis opened this issue Jan 8, 2019 · 4 comments

Comments

@russelldavis
Copy link

Why isn't the behavior enabled by --namespace-packages on by default? Is it because it's new/unstable, and will eventually become the default? (If so, can the docs be updated to reflect that?)

@gvanrossum
Copy link
Member

It has some downsides too, e.g. it means mypy can't resolve the package to which a file belongs when it's a namespace package (because there's no __init__.py to recognize it as a package). So it's not going to become the default.

@russelldavis
Copy link
Author

Got it, thanks. Can the docs be updated to explain the downsides?

@gvanrossum
Copy link
Member

Can you suggest a PR?

@russelldavis
Copy link
Author

For posterity, here's the proposal for enabling this by default: #8584

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

No branches or pull requests

2 participants