| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request systematically updates several core Python dependencies to their latest stable versions. The updates encompass significant feature enhancements in google-cloud-pubsub and google-cloud-storage, a major version upgrade for pandas introducing breaking changes and new paradigms, and a substantial pytest update with new testing features and configuration options. This ensures the project benefits from the latest improvements, security fixes, and maintains compatibility with modern Python environments. Highlights
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here. Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
Sorry, something went wrong.
There was a problem hiding this comment.
This pull request updates several dependencies, including google-cloud-pubsub, google-cloud-storage, pandas, and pytest. While most updates are straightforward, the upgrades for pandas to 3.0.1 and pytest to 9.0.2 introduce compatibility issues with the Python versions used in your test environments. Both of these new major versions have dropped support for older Python versions (Python < 3.11 for pandas 3.x and Python < 3.10 for pytest 9.x). The requirements.txt and requirements-test.txt files need to be adjusted to use the new versions only for compatible Python interpreters, while retaining the older versions for the rest. I have left specific comments with suggestions to fix these critical issues that would otherwise break your CI builds.
Sorry, something went wrong.
| @@ -1,4 +1,4 @@ | |||
| pytest===7.4.4; python_version == '3.7' | |||
| pytest==8.3.5; python_version >= '3.8' | |||
| pytest==9.0.2; python_version >= '3.8' | |||
There was a problem hiding this comment.
pytest 9.x requires Python 3.10 or newer, but this line attempts to install it for Python 3.8 and 3.9 as well, which will cause your build to fail for those versions. You should restrict this version to Python 3.10+.
To maintain support for older Python versions in your test matrix, you'll also need to add a line for pytest 8.x. Please add the following line before this one:
pytest==8.3.5; python_version >= '3.8' and python_version < '3.10'
pytest==9.0.2; python_version >= '3.10'
Sorry, something went wrong.
| pandas===1.3.5; python_version == '3.7' | ||
| pandas===2.0.3; python_version == '3.8' | ||
| pandas==2.2.3; python_version >= '3.9' | ||
| pandas==3.0.1; python_version >= '3.9' |
There was a problem hiding this comment.
pandas 3.x requires Python 3.11 or newer. This line attempts to install it for Python 3.9 and 3.10, which will cause build failures. You should restrict this version to Python 3.11+.
To maintain support for Python 3.9 and 3.10, you should add a line to continue using pandas 2.x for those versions. Please add the following line before this one:
pandas==2.2.3; python_version >= '3.9' and python_version < '3.11'
pandas==3.0.1; python_version >= '3.11'
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR contains the following updates:
Release Notes
googleapis/google-cloud-python (google-cloud-pubsub)v2.36.0: google-cloud-pubsub: v2.36.0
Compare Source
Features
v2.35.0: google-cloud-bigquery-storage 2.35.0
Features
v2.34.0: google-cloud-bigquery-storage 2.34.0
Features
Bug Fixes
Deprecate credentials_file argument (bd0f5422)
Require grpcio >= 1.33.2 (bd0f5422)
Require grpcio >= 1.75.1 for Python 3.14 (bd0f5422)
v2.33.0: google-cloud-speech: v2.33.0
Features
Documentation
v2.32.0: google-cloud-speech: v2.32.0
Features
Documentation
v2.31.1: google-cloud-speech: v2.31.1
Bug Fixes
v2.31.0: google-cloud-texttospeech: v2.31.0
Features
v2.30.0: google-api-core: v2.30.0
Bug Fixes
v2.29.1: google-cloud-monitoring 2.29.1
Bug Fixes
- fix mypy errors (#15494) (1f4c2862)
googleapis/python-storage (google-cloud-storage)v3.10.1
Compare Source
Bug Fixes
v3.10.0
Compare Source
Features
Perf Improvments
Bug Fixes
v3.9.0
Compare Source
Features
Bug Fixes
v3.8.0
Compare Source
Features
Bug Fixes
v3.7.0
Compare Source
Features
Bug Fixes
v3.6.0
Compare Source
Features
Bug Fixes
v3.5.0
Compare Source
Features
Bug Fixes
v3.4.1
Compare Source
Bug Fixes
v3.4.0
Compare Source
Features
Bug Fixes
v3.3.1
Compare Source
Bug Fixes
v3.3.0
Compare Source
Features
Bug Fixes
Documentation
v3.2.0
Compare Source
Features
v3.1.1
Compare Source
Bug Fixes
Documentation
- Move quickstart to top of readme (#1451) (53257cf)
- Update README to break infinite redirect loop (#1450) (03f1594)
pandas-dev/pandas (pandas)v3.0.2: pandas 3.0.2
Compare Source
We are pleased to announce the release of pandas 3.0.2.
This is a patch release in the 3.0.x series and includes some regression fixes and bug fixes. We recommend that all users of the 3.0.x series upgrade to this version.
See the full whatsnew for a list of all the changes.
Pandas 3.0 supports Python 3.11 and higher.
The release can be installed from PyPI:
Or from conda-forge
Please report any issues with the release on the pandas issue tracker.
Thanks to all the contributors who made this release possible.
v3.0.1: pandas 3.0.1
Compare Source
We are pleased to announce the release of pandas 3.0.1.
This is a patch release in the 3.0.x series and includes some regression fixes and bug fixes. We recommend that all users of the 3.0.x series upgrade to this version.
See the full whatsnew for a list of all the changes.
Pandas 3.0.0 supports Python 3.11 and higher.
The release can be installed from PyPI:
Or from conda-forge
Please report any issues with the release on the pandas issue tracker.
Thanks to all the contributors who made this release possible.
v3.0.0: pandas 3.0.0
Compare Source
We are pleased to announce the release of pandas 3.0.0, a major release from the pandas 2.x series. This release includes some new features, bug fixes, and performance improvements, as well as possible breaking changes.
The pandas 3.0 release removed a functionality that was deprecated in previous releases. It is recommended to first upgrade to pandas 2.3 and to ensure your code is working without warnings, before upgrading to pandas 3.0.
Highlights include:
See the full whatsnew for a list of all the changes.
Pandas 3.0.0 supports Python 3.11 and higher.
The release can be installed from PyPI
Or from conda-forge
Please report any issues with the release on the pandas issue tracker.
Thanks to all the contributors who made this release possible.
v2.3.3: Pandas 2.3.3
Compare Source
We are pleased to announce the release of pandas 2.3.3.
This release includes some improvements and fixes to the future string data type (preview feature for the upcoming pandas 3.0). We recommend that all users upgrade to this version.
See the full whatsnew for a list of all the changes.
Pandas 2.3.3 supports Python 3.9 and higher, and is the first release to support Python 3.14.
The release will be available on the conda-forge channel:
Or via PyPI:
Please report any issues with the release on the pandas issue tracker.
Thanks to all the contributors who made this release possible.
v2.3.2: Pandas 2.3.2
Compare Source
We are pleased to announce the release of pandas 2.3.2.
This release includes some improvements and fixes to the future string data type (preview feature for the upcoming pandas 3.0). We recommend that all users upgrade to this version.
See the full whatsnew for a list of all the changes.
Pandas 2.3.2 supports Python 3.9 and higher.
The release will be available on the conda-forge channel:
Or via PyPI:
Please report any issues with the release on the pandas issue tracker.
Thanks to all the contributors who made this release possible.
v2.3.1: Pandas 2.3.1
Compare Source
We are pleased to announce the release of pandas 2.3.1.
This release includes some improvements and fixes to the future string data type (preview feature for the upcoming pandas 3.0). We recommend that all users upgrade to this version.
See the full whatsnew for a list of all the changes.
Pandas 2.3.1 supports Python 3.9 and higher.
The release will be available on the conda-forge channel:
Or via PyPI:
Please report any issues with the release on the pandas issue tracker.
Thanks to all the contributors who made this release possible.
v2.3.0: Pandas 2.3.0
Compare Source
We are pleased to announce the release of pandas 2.3.0.
This release includes some new features, bug fixes, and performance improvements. We recommend that all users upgrade to this version.
See the full whatsnew for a list of all the changes.
Pandas 2.3.0 supports Python 3.10 and higher.
The release will be available on the defaults and conda-forge channels:
Or via PyPI:
Please report any issues with the release on the pandas issue tracker.
Thanks to all the contributors who made this release possible.
pytest-dev/pytest (pytest)v9.0.2
Compare Source
pytest 9.0.2 (2025-12-06)
Bug fixes
#13896: The terminal progress feature added in pytest 9.0.0 has been disabled by default, except on Windows, due to compatibility issues with some terminal emulators.
You may enable it again by passing -p terminalprogress. We may enable it by default again once compatibility improves in the future.
Additionally, when the environment variable TERM is dumb, the escape codes are no longer emitted, even if the plugin is enabled.
#13904: Fixed the TOML type of the tmp_path_retention_count settings in the API reference from number to string.
#13946: The private config.inicfg attribute was changed in a breaking manner in pytest 9.0.0.
Due to its usage in the ecosystem, it is now restored to working order using a compatibility shim.
It will be deprecated in pytest 9.1 and removed in pytest 10.
#13965: Fixed quadratic-time behavior when handling unittest subtests in Python 3.10.
Improved documentation
v9.0.1
Compare Source
pytest 9.0.1 (2025-11-12)
Bug fixes
Packaging updates and notes for downstreams
version string can be passed into its package_env through
the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
variable as a part of the release process -- by webknjaz.
Contributor-facing changes
creating GitHub Releases without having a Git checkout on
disk -- by bluetech and webknjaz.
version string can be passed into its package_env through
the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
variable as a part of the release process -- by webknjaz.
v9.0.0
Compare Source
pytest 9.0.0 (2025-11-05)
New features
#1367: Support for subtests has been added.
subtests <subtests> are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.
Example:
Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.
In addition, unittest.TestCase.subTest is now also supported.
This feature was originally implemented as a separate plugin in pytest-subtests, but since then has been merged into the core.
#13743: Added support for native TOML configuration files.
While pytest, since version 6, supports configuration in pyproject.toml files under [tool.pytest.ini_options],
it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings.
Now, pytest supports the native TOML data model.
In pyproject.toml, the native TOML configuration is under the [tool.pytest] table.
The [tool.pytest.ini_options] table remains supported, but both tables cannot be used at the same time.
If you prefer to use a separate configuration file, or don't use pyproject.toml, you can use pytest.toml or .pytest.toml:
The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.
See config file formats for full details.
#13823: Added a "strict mode" enabled by the strict configuration option.
When set to true, the strict option currently enables
The individual strictness options can be explicitly set to override the global strict setting.
The previously-deprecated --strict command-line flag now enables strict mode.
If pytest adds new strictness options in the future, they will also be enabled in strict mode.
Therefore, you should only enable strict mode if you use a pinned/locked version of pytest,
or if you want to proactively adopt new strictness options as they are added.
See strict mode for more details.
#13737: Added the strict_parametrization_ids configuration option.
When set, pytest emits an error if it detects non-unique parameter set IDs,
rather than automatically making the IDs unique by adding 0, 1, ... to them.
This can be particularly useful for catching unintended duplicates.
#13072: Added support for displaying test session progress in the terminal tab using the OSC 9;4; ANSI sequence.
When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,
you'll see the progress in the terminal tab or window,
allowing you to monitor pytest's progress at a glance.
This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows:
#478: Support PEP420 (implicit namespace packages) as --pyargs target when consider_namespace_packages is true in the config.
Previously, this option only impacted package imports, now it also impacts tests discovery.
#13678: Added a new faulthandler_exit_on_timeout configuration option set to "false" by default to let faulthandler interrupt the pytest process after a timeout in case of deadlock.
Previously, a faulthandler timeout would only dump the traceback of all threads to stderr, but would not interrupt the pytest process.
-- by ogrisel.
#13829: Added support for configuration option aliases via the aliases parameter in Parser.addini() <pytest.Parser.addini>.
Plugins can now register alternative names for configuration options,
allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options.
The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file.
Improvements in existing functionality
#13330: Having pytest configuration spread over more than one file (for example having both a pytest.ini file and pyproject.toml with a [tool.pytest.ini_options] table) will now print a warning to make it clearer to the user that only one of them is actually used.
-- by sgaist
#13574: The single argument --version no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version.
Passing --version twice (e.g., pytest --version --version) retains the original behavior, showing both the pytest version and plugin information.
#13823: Added strict_xfail as an alias to the xfail_strict option,
strict_config as an alias to the --strict-config flag,
and strict_markers as an alias to the --strict-markers flag.
This makes all strictness options consistently have configuration options with the prefix strict_.
#13700: --junitxml no longer prints the generated xml file summary at the end of the pytest session when --quiet is given.
#13732: Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem.
#13859: Clarify the error message for pytest.raises() when a regex match fails.
#13861: Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be <expected>, but got <actual>". Now, it is "Expected <expected>, but got <actual>".
Removals and backward incompatible breaking changes
#12083: Fixed a bug where an invocation such as pytest a/ a/b would cause only tests from a/b to run, and not other tests under a/.
The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled:
If you rely on these behaviors, consider using --keep-duplicates <duplicate-paths>, which retains its existing behavior (including the bug).
#13719: Support for Python 3.9 is dropped following its end of life.
#13766: Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables $CI or $BUILD_NUMBER was defined;
now, CI mode is only activated if at least one of those variables is defined and set to a non-empty value.
#13779: PytestRemovedIn9Warning deprecation warnings are now errors by default.
Following our plan to remove deprecated features with as little disruption as
possible, all warnings of type PytestRemovedIn9Warning now generate errors
instead of warning messages by default.
The affected features will be effectively removed in pytest 9.1, so please consult the
deprecations section in the docs for directions on how to update existing code.
In the pytest 9.0.X series, it is possible to change the errors back into warnings as a
stopgap measure by adding this to your pytest.ini file:
But this will stop working when pytest 9.1 is released.
If you have concerns about the removal of a specific feature, please add a
comment to 13779.
Deprecations (removal in next major release)
Users should migrate to native namespace packages (420).
See monkeypatch-fixup-namespace-packages for details.
Bug fixes
#13445: Made the type annotations of pytest.skip and friends more spec-complaint to have them work across more type checkers.
#13537: Fixed a bug in which ExceptionGroup with only Skipped exceptions in teardown was not handled correctly and showed as error.
#13598: Fixed possible collection confusion on Windows when short paths and symlinks are involved.
#13716: Fixed a bug where a nonsensical invocation like pytest x.py[a] (a file cannot be parametrized) was silently treated as pytest x.py. This is now a usage error.
#13722: Fixed a misleading assertion failure message when using pytest.approx on mappings with differing lengths.
#13773: Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures.
#13816: Fixed pytest.approx which now returns a clearer error message when comparing mappings with different keys.
#13849: Hidden .pytest.ini files are now picked up as the config file even if empty.
This was an inconsistency with non-hidden pytest.ini.
[#13865](https://redirect.github.com/pyte
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.