-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
ModuleNotFoundError: No module named 'adal' #13996
Comments
Same issue with msrestazure package.
|
It looks like msrestazure has a proper requirement on adal: https://github.com/Azure/msrestazure-for-python/blob/master/setup.py#L54 It seems that azure-common should have a similar requirement on adal and msrestazure in setup.py to ensure dependency tree is installed accordingly. |
@scbedd is this something you are working on? |
Hi @smarlowucf azure-sdk-for-python/sdk/core/azure-common/azure/common/credentials.py Lines 115 to 122 in 8b749c2
We did have a extra node to install like We could though make the same ImportError catcher in Thanks! |
Hi, @lmazuel thanks for the explanation. IMHO it's not nice to force downstream packages to have dependencies on packages that really are used upstream. This can become very troublesome to properly manage. The downstream packages now have to add all this in their own requirements.txt:
Which is quite confusing and inaccurate because adal and msrestazure are not used in those packages directly. |
This issue has only come up recently which means a backwards incompatible change was made somewhere in the Azure packages. In my case I have requirements on:
Thus while some backwards incompatible changes are being avoided (azure-common) it seems that is not the case in all packages? |
Re-testing this with 1.1.26 gives the following error:
Which is the best we can do today considering our need for backward compatibility, and the fact that more and more packages are actually incompatible with "get_client_from_auth_file" nowadays (see #15075). Also, if you have a package compatible, the package in question will install "msrest" anyway. Closing this issue giving the preceding reasoning. |
Hi @lmazuel can you please point me to documentation describing how to use the new authentication route? I'm very confused and have no luck finding any examples or docs. It would be helpful to see an entire workflow including authentication of a client. For example the code that worked before:
If |
Describe the bug
Attempting to use get_client_from_auth_file function from azure-common client_factory module leads to import error.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The adal package should be required when installing azure-common as it is imported and used in the code. Thus preventing a module not found error when using get_client_from_auth_file.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
The text was updated successfully, but these errors were encountered: