Skip to content

[meta issue] confusing Python package strategy #1325

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
lostmygithubaccount opened this issue Feb 8, 2021 · 5 comments
Closed

[meta issue] confusing Python package strategy #1325

lostmygithubaccount opened this issue Feb 8, 2021 · 5 comments
Labels
2.0 Planned for next major ADO Issue is documented on MSFT ADO for internal tracking MLOps product-gap product gaps

Comments

@lostmygithubaccount lostmygithubaccount self-assigned this Feb 8, 2021
@lostmygithubaccount lostmygithubaccount added MLOps product-gap product gaps 2.0 Planned for next major labels Feb 8, 2021
@lostmygithubaccount
Copy link
Contributor Author

"the v2 core SDK will be named "azure-ml" and we [will] have a very very high bar on releasing new packages"

@lostmygithubaccount
Copy link
Contributor Author

#516

@lostmygithubaccount
Copy link
Contributor Author

#1341

@lostmygithubaccount
Copy link
Contributor Author

#1355

@lostmygithubaccount
Copy link
Contributor Author

tangentially related, all of our issues with dependencies - pyjwt, cryptography, pip, pyarrow, etc.: #1379

@v-strudm-msft v-strudm-msft added the ADO Issue is documented on MSFT ADO for internal tracking label Apr 24, 2021
@lostmygithubaccount lostmygithubaccount removed their assignment Jul 23, 2022
@lostmygithubaccount lostmygithubaccount closed this as not planned Won't fix, can't repro, duplicate, stale Jun 22, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
2.0 Planned for next major ADO Issue is documented on MSFT ADO for internal tracking MLOps product-gap product gaps
Projects
None yet
Development

No branches or pull requests

2 participants