-
Notifications
You must be signed in to change notification settings - Fork 4
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
Support implicit namespaces #126
Conversation
Since Python 3.3 one does not need to create `__init__.py` files to mark a folder to be part of a namespace, but the simple presence of a python file deep inside it is enough to create it. Moreover, since `setuptools` 62.3.0 it is officially discouraged to use the old `pkg_resources` namespace technique.
a126ead
to
22b780e
Compare
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.
Looks handy!
May I merge and release then? 😄 I'm never comfortable doing that without asking and getting approval 😅 But given that plenty of packages are configured with |
Release is fine.
Reinout
|
|
Closes #120
Seems that all the discussion we had with @ericof at the issue is not so relevant, as we are already using the
.egg-info
information to know where the source code is located 🎉