-
Notifications
You must be signed in to change notification settings - Fork 104
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
Unable to use azure SDKs with python #164
Comments
I need a bit more context please. How was the python worker installed? |
Just following the quickstart here |
Link didn’t work but it’s the “create function via CLI” one |
Which version of core tools are you running? @ahmelsayed can you confirm that we do not use the development mode install for the python worker ( |
@jeffhollan what is the version of the core tools you're using? Can you also share your |
Tested this on latest func cli and it's working now so can close. As any FYI my requirements.txt when not working had this:
But now has this
|
I actually ran into this reference to GitHub too, had issues when publishing when this was still in the requirement.txt file. Wrote something about it here, where I was struggling as well. Maybe someone can explain why it is setup like this and not just a normal reference as Jeff says here as well? Update: Apparently this is already changed in the latest version of the cli. Just created a new function and my requirements are now listed as:
|
@rvanmaanen thanks for blogging about this! Just ran through your post and most of the rough edges you ran into earlier should now be fixed. Let us know about your experience when you give it a shot next. Happy to connect further on any feedback and recommendations you might have :) PS Python on v2 is not yet officially supported hence it's not mentioned on the docs. We're treating the feature as still in-development. |
Created a vanilla HTTP function (works):
I then installed the Azure SDK
When I try to reference one of these SDKs it throws errors for naming conficts
The text was updated successfully, but these errors were encountered: