Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Dependency problems (docker/pywin32 and ruamel.yaml)

Open
#1,833 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, docker, python
Domain
devops, machine-learning

Research direction

No target files or tests are named. Start by locating the dependency declarations for azureml-core and azureml-pipeline-core, then reproduce installation on Windows with a current pip; done means the reported pywin32 and ruamel.yaml conflicts no longer block the stated Azure ML workflows.

Written by the indexing model from the issue text.

Description

Hello everyone! I'm having problems with Azure packages because apparently, they have some broken dependencies. I'm reporting the following problems:

  • docker: Required by azureml-core, docker is pinned to a version lower than 6.0.0 . However, older versions of this library pin pywin32 227, and any version of pywin32 below 300 breaks default_azure_credential when using it in Windows. This would automatically break Azure CLI Login (in my case this is happening). Also, version 6.0.0 fixes pywin32 I think azure should just update it to 6.0.0 in order to fix the problem
  • ruamel.yaml: The package azureml-pipeline-core depends on ruamel.yaml pinned on a version below 16. This lib requires to compile some binaries in C while installing, and any version below 16 uses an installation method not supported by pip versions over 20.1. To solve this, I had to downgrade pip, or install it using poetry, which is a package manager able to fix this bug

Considering all AzureML SDK packages were developed using modular packages, I really recommend using Poetry to manage dependencies, and dependabot (or something similar) to update automatically update deps. it would reduce installation time, and would prevent future conflicts.

I think Azure should fix these problems before fully migrating to SDK v2 since there are some features still in beta.

Related links:

Dominant language
Jupyter Notebook
Stars
4.4k
Forks
2.6k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/MachineLearningNotebooks

All issues in Azure/MachineLearningNotebooks

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.