-
Notifications
You must be signed in to change notification settings - Fork 313
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
Use "com" folder as an implicit namespace #408
Labels
Comments
Hi @mxmrlt This is an unfortunate case of "missing init.py trap". We are exploring the options like updating the SDK and its dependencies to use Implicit Namespace packages, removing "com" form namespace package etc. Once the approach is finalized, We will update the ticket with target dates by when the fix will be available. Thanks |
The issue will be fixed in next SDK 8.0U3 release |
8.0U3 is released. Closing the issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
While using this package as a dependency it is impossible to use another one which also has
com
folder in its source code.The problem occurs mostly in editable installation mode.
These sub-packages contain an
__init__.py
file making fail any other packages withcom.company
namespace :vapi-common-client-.zip
vcenter_bindings-.zip
vmwarecloud_aws-.zip
vmwarecloud_draas-.zip
The
__init__.py
file :There shouldn't be any
__init__.py
file in the "com" folder. This latter is "universal" and can be used by many others.Reproduction steps
com.compagny
namespacepython -c "from com.company.mypackage.mymodule import my_function, my_class"
Traceback (most recent call last): File "<string>", line 1, in <module> ModuleNotFoundError: No module named 'com.company'
Expected behavior
should be possible.
Additional context
No response
The text was updated successfully, but these errors were encountered: