Scheduled weekly dependency update for week 08 #657
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,7 @@ | ||
| sphinx==9.1.0 | ||
| furo==2025.12.19 | ||
| sphinx-autobuild==2025.8.25 | ||
| sphinx-copybutton==0.5.2 | ||
| sphinx-sitemap==2.9.0 | ||
| sphinx-click==6.2.0 | ||
| sphinx-autodoc-typehints==3.6.3 | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,9 +1,9 @@ | ||
| setuptools==82.0.0 | ||
|
There was a problem hiding this comment. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Check for direct pkg_resources usage in Python source files
rg "import pkg_resources|from pkg_resources" --type=py -n
# Also check for pkg_resources in setup.py or setup.cfg
fd -e "setup.py" -o -e "setup.cfg" -o -e "pyproject.toml" | while read f; do
if [ -f "$f" ]; then
echo "=== $f ==="
grep -n "pkg_resources" "$f" 2>/dev/null || echo "No pkg_resources found"
fi
done
# Check for any egg_info or dist-info references that might implicitly use pkg_resources
rg "egg.info|dist.info" --type=py -n | head -20Repository: DagsHub/client Length of output: 174 🏁 Script executed: #!/bin/bash
# Check for direct pkg_resources usage in Python source files
echo "=== Searching for pkg_resources imports ==="
rg "import pkg_resources|from pkg_resources" --type=py -n
echo -e "\n=== Checking setup.py files ==="
find . -name "setup.py" -type f | head -20 | xargs grep -n "pkg_resources" 2>/dev/null || echo "No pkg_resources in setup.py files"
echo -e "\n=== Checking setup.cfg files ==="
find . -name "setup.cfg" -type f | head -20 | xargs grep -n "pkg_resources" 2>/dev/null || echo "No pkg_resources in setup.cfg files"
echo -e "\n=== Checking pyproject.toml files ==="
find . -name "pyproject.toml" -type f | head -20 | xargs grep -n "pkg_resources" 2>/dev/null || echo "No pkg_resources in pyproject.toml files"
echo -e "\n=== Checking requirements files ==="
find . -name "requirements*.txt" -type f | xargs grep -n "pkg_resources" 2>/dev/null || echo "No pkg_resources in requirements files"
echo -e "\n=== Repository structure (to understand project) ==="
ls -laRepository: DagsHub/client Length of output: 1752 🏁 Script executed: #!/bin/bash
# Read setup.py to check dependencies
echo "=== setup.py content ==="
cat setup.py
echo -e "\n=== pyproject.toml content ==="
cat pyproject.toml
echo -e "\n=== requirements-dev.txt content ==="
cat requirements-dev.txtRepository: DagsHub/client Length of output: 2539
While |
||
| pytest==9.0.2 | ||
|
There was a problem hiding this comment. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Search for deprecated pytest patterns that would break in pytest 9.0.2
echo "=== Searching for py.path.local usage ==="
rg -n "py\.path|py_path|\.local\(" --type=py -C2 2>/dev/null | head -50
echo -e "\n=== Searching for yield_fixture ==="
rg -n "yield_fixture" --type=py -C2 2>/dev/null
echo -e "\n=== Searching for deprecated hook parameters ==="
rg -n "pytest_ignore_collect|pytest_collect_file|pytest_pycollect_makemodule|pytest_report_header|pytest_report_collectionfinish" --type=py -C3 2>/dev/null | head -50
echo -e "\n=== Checking for conftest.py files ==="
find . -name "conftest.py" -type f 2>/dev/null
echo -e "\n=== Checking Python version requirements ==="
if [ -f "setup.py" ]; then
echo "=== setup.py ===" && cat setup.py | head -30
fi
if [ -f "pyproject.toml" ]; then
echo "=== pyproject.toml ===" && cat pyproject.toml | head -50
fi
if [ -f "setup.cfg" ]; then
echo "=== setup.cfg ===" && cat setup.cfg | head -30
fiRepository: DagsHub/client Length of output: 1363 🏁 Script executed: #!/bin/bash
# Get complete Python version requirements
echo "=== Full setup.py python_requires ==="
grep -A 50 "python_requires\|setup(" setup.py | head -60
echo -e "\n=== Full pyproject.toml ==="
cat pyproject.toml 2>/dev/null | head -100
echo -e "\n=== Content of conftest.py files ==="
for f in ./tests/data_engine/conftest.py ./tests/dda/conftest.py ./tests/dda/filesystem/conftest.py ./tests/dda/upload/conftest.py ./tests/model_loading/conftest.py; do
if [ -f "$f" ]; then
echo "--- $f ---"
wc -l "$f"
cat -n "$f" | head -50
fi
done
echo -e "\n=== Check for any pytest imports/configs ==="
rg -n "import pytest|from pytest|@pytest" --type=py --max-count=20Repository: DagsHub/client Length of output: 14395 🏁 Script executed: #!/bin/bash
# Verify Python 3.9 compatibility issue with pytest 9.0.2
echo "=== Checking pytest 9.0.2 Python requirements ==="
rg -n "python" requirements-dev.txt -i
echo -e "\n=== Checking if Python 3.9 is explicitly tested in CI ==="
find . -name "*.yml" -o -name "*.yaml" | xargs grep -l "python\|pytest" 2>/dev/null | head -5
if [ -f ".github/workflows/test.yml" ] || [ -f ".github/workflows/tests.yml" ]; then
echo "=== GitHub Actions test workflow ==="
cat .github/workflows/test.yml 2>/dev/null || cat .github/workflows/tests.yml 2>/dev/null | head -50
fi
echo -e "\n=== Check tox.ini or similar test configuration ==="
find . -name "tox.ini" -o -name "pytest.ini" -o -name "setup.cfg" | xargs cat 2>/dev/null | head -50Repository: DagsHub/client Length of output: 507 🏁 Script executed: #!/bin/bash
# Check CI/CD workflow to see Python versions being tested
echo "=== GitHub Actions python-package.yml ==="
cat .github/workflows/python-package.yml
echo -e "\n=== Checking all pytest version references ==="
rg "pytest" requirements*.txtRepository: DagsHub/client Length of output: 1569
The upgrade to pytest 9.0.2 breaks the project's Python 3.9 support: pytest 9.0 dropped Python 3.9 support, requiring Python 3.10 or later. Your CI workflow currently tests against Python 3.9, 3.10, 3.11, 3.12, and 3.13, and the package's Options:
Additional breaking changes in pytest 9.0 (for reference): |
||
| respx==0.22.0 | ||
| pytest-git==1.8.0 | ||
| pytest-env==1.5.0 | ||
| pytest-mock==3.15.1 | ||
| fiftyone==1.13.2 | ||
| datasets==4.5.0 | ||
| ultralytics==8.4.14 | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: DagsHub/client
Length of output: 180
🏁 Script executed:
Repository: DagsHub/client
Length of output: 540
🏁 Script executed:
Repository: DagsHub/client
Length of output: 310
🏁 Script executed:
Repository: DagsHub/client
Length of output: 3149
🌐 Web query:
Sphinx 9.1.0 release notes Python 3.11 support breaking changes💡 Result:
Sphinx 9.1.0 was released Dec 31, 2025 [1].
Python 3.11 support
Breaking changes / compatibility-impacting changes (9.1.0)
Sources: Sphinx changelog (9.1.0) [1], PyPI project metadata [2].
🌐 Web query:
Sphinx 9.0 autodoc breaking changes autodoc_default_flags deprecated💡 Result:
Sphinx 9.0 autodoc breaking / incompatible changes
sphinx.ext.autodocwas “substantially rewritten” in Sphinx 9.0.0 (released Nov 30, 2025), and Sphinx explicitly warns there may be incompatible changes in edge cases, especially for extensions that interact with autodoc internals. To mitigate this, Sphinx 9 addsautodoc_use_legacy_class_basedto switch back to the pre-9.0 implementation. [1]autodoc_default_flagsdeprecation (what to do now)autodoc_default_flagshas been deprecated since Sphinx 1.8.0b1 (i.e., this is not new to 9.0). [2]autodoc_default_options, a dict applied to all autodoc directives;NoneorTruemeans “flag enabled”. [3]Typical migration:
[2][3]
Sources: Sphinx 9.0 changelog [1], Sphinx 1.8 changelog (deprecates
autodoc_default_flags) [2], current autodoc config docs (autodoc_default_options) [3].Update
autodoc_default_flagstoautodoc_default_optionsand test autodoc compatibilitySphinx 9.1.0 (released Dec 31, 2025) involves significant changes to
sphinx.ext.autodoc:conf.pyuses the deprecatedautodoc_default_flags = ["inherited-members"](line 68), which has been deprecated since Sphinx 1.8.0b1. This must be migrated toautodoc_default_options:Migration example
After the upgrade, test autodoc output carefully, especially with
sphinx_autodoc_typehints(line 29), which may require compatibility adjustments for the rewritten autodoc internals. Useautodoc_use_legacy_class_based = Trueif you encounter autodoc behavior changes that break documentation generation.