Skip to content

Pin pytest to latest version 9.1.0 #580

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.

Sign up for GitHub

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

Open
pyup-bot wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Pin pytest to latest version 9.1.0 #580

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/requirements_dev.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
pytest
pytest==9.1.0

@coderabbitai coderabbitai Bot Jun 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check if project declares a minimum Python version that is compatible with pytest 9.1.0 (requires 3.10+)
# Search for Python version constraints in project configuration files

fd -e pyproject.toml -e setup.py -e setup.cfg -e tox.ini | head -5 | while read f; do
  echo "=== $f ==="
  cat "$f" | grep -A 5 -B 5 -i "python.*version\|requires-python" || echo "(no version constraint found)"
done

Repository: salimfadhley/dockerized_python_playground

Length of output: 67

🏁 Script executed:

# First, check what files actually exist in the repo
git ls-files | grep -E "(pyproject|setup|tox|Dockerfile|\.yml|\.yaml|requirements)" | head -20

Repository: salimfadhley/dockerized_python_playground

Length of output: 187

🏁 Script executed:

# Read the complete requirements_dev.txt to see all dependencies
cat src/requirements_dev.txt

Repository: salimfadhley/dockerized_python_playground

Length of output: 124

🏁 Script executed:

# Check for any Python version information in root config files
ls -la | grep -E "\.(py|toml|cfg|ini|txt|md)$"

Repository: salimfadhley/dockerized_python_playground

Length of output: 143

🏁 Script executed:

# Search for Python version references anywhere in the codebase
rg -i "python.*3\.[0-9]|3\.[0-9].*python" --type txt --type md --type yml --type yaml | head -20

Repository: salimfadhley/dockerized_python_playground

Length of output: 113

🏁 Script executed:

cat Dockerfile

Repository: salimfadhley/dockerized_python_playground

Length of output: 266

🏁 Script executed:

cat .travis.yml

Repository: salimfadhley/dockerized_python_playground

Length of output: 218

🏁 Script executed:

cat src/setup.py

Repository: salimfadhley/dockerized_python_playground

Length of output: 1166

🏁 Script executed:

# Search for any Python version specifications
rg -i "python" src/ --type txt --type py -B 2 -A 2 | head -40

Repository: salimfadhley/dockerized_python_playground

Length of output: 654

pytest 9.1.0 is incompatible with the project's target Python version.

The CI configuration (.travis.yml) specifies Python 3.6 as the test environment, but pytest 9.1.0 requires Python 3.10 or higher. This will cause test execution to fail. Either downgrade pytest to a version supporting Python 3.6 (e.g., pytest 7.x), or update the target Python version to 3.10+ in the CI configuration and project documentation.

Additionally, mypy 0.670 is from 2019 and likely incompatible with pytest 9.1.0. Consider updating to a modern mypy version.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/requirements_dev.txt` at line 1, The pytest version 9.1.0 specified in
the requirements is incompatible with Python 3.6, which is the target version in
the CI configuration. Either downgrade pytest to a version compatible with
Python 3.6 (such as pytest 7.x) in the requirements file, or update the Python
version in the CI configuration to 3.10 or higher. Additionally, update mypy to
a modern version since mypy 0.670 is outdated and likely incompatible with
current pytest versions.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify mypy-pytest compatibility by checking recent mypy releases and compatibility notes
# Look for any CI configuration that validates this combination

fd -e .github -e pytest.ini -e tox.ini -type f | xargs grep -l "mypy\|pytest" 2>/dev/null | head -3
cat .github/workflows/*.yml 2>/dev/null | grep -A 3 -B 3 "mypy\|pytest" || echo "No workflow config found"

Repository: salimfadhley/dockerized_python_playground

Length of output: 299

🏁 Script executed:

cat -n src/requirements_dev.txt

Repository: salimfadhley/dockerized_python_playground

Length of output: 145

🏁 Script executed:

# Search for mypy in the repository
fd -type f -name "*.txt" | xargs grep -l "mypy" 2>/dev/null

Repository: salimfadhley/dockerized_python_playground

Length of output: 258

🏁 Script executed:

# Look for pyproject.toml, setup.py, or tox configuration
fd -type f \( -name "pyproject.toml" -o -name "setup.py" -o -name "tox.ini" -o -name ".mypy.ini" \)

Repository: salimfadhley/dockerized_python_playground

Length of output: 256

🏁 Script executed:

# Check for GitHub workflows more carefully
fd -type f -path "*/.github/workflows/*"

Repository: salimfadhley/dockerized_python_playground

Length of output: 256

🏁 Script executed:

# Find GitHub workflow files
find .github/workflows -type f 2>/dev/null || echo "No workflows directory found"

Repository: salimfadhley/dockerized_python_playground

Length of output: 114

🌐 Web query:

mypy 0.670 pytest 9.1.0 compatibility

💡 Result:

Mypy 0.670 and pytest 9.1.0 are not compatible due to the significant age gap between their release dates and the evolution of both projects [1][2][3][4]. Mypy 0.670 was released on February 8, 2019 [1][2]. In contrast, pytest 9.1.0 is a much newer release within the 9.x series (with pytest 9.0.0 released in November 2025) [5][6][7]. Key compatibility considerations include: 1. Significant Breaking Changes: Over the seven years separating these versions, pytest has undergone numerous internal API changes, including the removal of deprecated features [8]. For instance, mypy's own internal test suite required updates to support pytest 8.0+, highlighting that an ancient version like 0.670 would be incompatible with the structure and requirements of pytest 9.x [8]. 2. Dependency Mismatches: Modern plugins and tooling infrastructure designed for pytest 9.x generally require much newer versions of mypy [9][10]. For example, community plugins like pytest-mypy and pytest-mypy-plugins typically list minimum dependencies for mypy that are significantly higher than 0.670 (e.g., mypy >= 1.0) [9][10]. If you are encountering issues, you should upgrade your mypy version to a modern release (e.g., 1.x or 2.x) to ensure compatibility with current pytest versions and modern Python syntax [11][12].

Citations:

🌐 Web query:

mypy 0.670 python type checking compatibility with modern pytest versions

💡 Result:

Mypy 0.670 is not compatible with modern pytest versions or modern Python environments [1][2][3]. Released in February 2019, mypy 0.670 is a legacy version [1][2]. It was designed for older Python environments (such as Python 3.4–3.7) [1][4] and lacks support for modern Python features, syntax, and type-checking improvements developed over the last several years. Key reasons for incompatibility include: 1. Integration Plugins: Modern pytest integration, such as the pytest-mypy plugin, requires significantly newer versions of mypy (typically mypy >= 1.0) [3]. Older versions of integration plugins that were compatible with 0.670 are deprecated and do not support current pytest versions (e.g., pytest 7.x or 8.x) [3]. 2. Dependency Conflicts: Mypy 0.670 relies on outdated dependencies like typed-ast [5], which are often incompatible with current Python versions (e.g., Python 3.10+), leading to installation and runtime errors. 3. Bug Fixes and Stability: Mypy 0.670 contains known issues and crashes (e.g., AssertionError, typeshed path errors) that have long been resolved in subsequent releases [6][7]. For any modern project, it is strongly recommended to use the latest stable version of mypy to ensure compatibility with recent Python versions and current testing frameworks.

Citations:

Mypy 0.670 is incompatible with pytest 9.1.0—update mypy to a supported version.

Mypy 0.670 (released February 2019) and pytest 9.1.0 (released 2025) are incompatible. Over the seven-year gap, pytest has undergone breaking changes that mypy 0.670 cannot support. Additionally, modern pytest integration plugins like pytest-mypy require mypy >= 1.0, and mypy 0.670 relies on deprecated dependencies (e.g., typed-ast) that fail on modern Python versions. Update mypy to at least 1.7+ or a later stable 1.x/2.x release to resolve compatibility issues and ensure proper type checking in your test environment.

Also applies to: 2-2

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/requirements_dev.txt` at line 1, The mypy version is pinned to 0.670,
which is incompatible with pytest 9.1.0 due to being seven years old and relying
on deprecated dependencies like typed-ast. Update the mypy version specification
to at least 1.7 or a later stable 1.x/2.x release to ensure compatibility with
the current pytest version and enable proper type checking in the test
environment.

mypy==0.670
pylint2junit