-
Notifications
You must be signed in to change notification settings - Fork 209
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
Import error when attempting to use azure.devops.v5_0.universal
#280
Labels
Comments
tedchamb
added a commit
that referenced
this issue
Oct 20, 2019
tedchamb
added a commit
that referenced
this issue
Oct 20, 2019
fix issue #280, fix naming of upack_api_client folder: universal becomes upack_api
tedchamb
added a commit
that referenced
this issue
Oct 20, 2019
5.1.0b5 - fix #280, fix a bunch of spelling in comments
@mariusvniekerk , thanks for reporting this issue. It is now fixed in release: https://github.com/microsoft/azure-devops-python-api/releases/tag/5.1.0b5 |
nechvatalp
pushed a commit
that referenced
this issue
Jul 26, 2024
5.1.0b5 - fix #280, fix a bunch of spelling in comments
pull bot
pushed a commit
to tooniez/azure-devops-python-api
that referenced
this issue
Jul 27, 2024
…rsal becomes upack_api
pull bot
pushed a commit
to tooniez/azure-devops-python-api
that referenced
this issue
Jul 27, 2024
fix issue microsoft#280, fix naming of upack_api_client folder: universal becomes upack_api
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
azure-devops-python-api/azure-devops/azure/devops/v5_1/universal/__init__.py
Line 10 in 1ada541
It seems as if there is an incorrect client referenced for this api. Same issue exists in v5_0
The text was updated successfully, but these errors were encountered: