Skip to content

Bump the python-packages group across 1 directory with 5 updates - #4

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/python-packages-23c0d2d492
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/python-packages-23c0d2d492

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the python-packages group with 5 updates in the / directory:

Package From To
watchdog 6.0.0 7.1.0
python-dateutil 2.9.0.post0 4.0.0
streamlit 1.66.1 1.67.0
pandas 3.0.6 3.1.1
pytest 9.1.1 9.2.0

Updates watchdog from 6.0.0 to 7.1.0

Release notes

Sourced from watchdog's releases.

7.1.0

  • [fsevents] Fix building the extension on PyPy 3.12 by updating the bundled pythoncapi_compat.h. (#1397)
  • [inotify] Create the inotify instance lazily so observer and polling imports succeed when the inotify instance limit is reached. (#1389)
  • [inotify] Reconcile recursively watched directories renamed before their source watch was registered, and simulate existing descendants so their initial changes are reported. (#1383)
  • [inotify] Reconcile recursive watches after the kernel reports an inotify queue overflow so subsequent filesystem changes are observed. (#654)
  • [inotify] Watch directories moved into a recursively watched directory from outside of it, so that changes inside them are reported. (#1094)
  • [inotify] Fix the inotify thread dying with a KeyError when a directory tree is copied or extracted into a recursively watched directory, which stopped all inotify observers in the process. (#1388)
  • [observers] Align BaseObserver with BaseThread by using on_thread_start() instead of overriding start(). (#286)
  • [watchmedo] Fix watchmedo generate-tricks-yaml output so that watchmedo tricks can load it: trick options are now nested under the trick name instead of under unsupported args/kwargs keys. (#1403)

💟 Thanks to our beloved contributors: @​BoboTiG, @​prateek-dagar, @​monosans, @​taltal-beep, @​Aschenbath, @​yangfan-yf-yf, @​alexruperez, @​PDGGK, @​Skeletor-Pirate

7.0.0

Breaking Changes

  • Drop support for Python 3.9 and 3.10.
  • [core] Changed pattern matching mechanism from using path.match() to path.full_match(). Users must update patterns to glob-like syntax: e.g., *.py to **/*.py. (#1101)
  • [core] Added FileAttribEvent and DirAttribEvent for file and directory metadata modifications (such as permissions or timestamps), separate from content modifications. These events no longer trigger on_modified(); implement on_attrib() to handle them. On Windows 10 (1709+) and Windows Server 2016+, ReadDirectoryChangesExW is used to differentiate attribute modifications, with fallback to ReadDirectoryChangesW on older versions or unsupported file shares. (#260)
  • [watchmedo] Changed the default --patterns value from "*" to "**", so the default matches absolute paths at any depth under the full_match() semantics introduced by #1101, and updated the CLI help text and docs to the **/ glob syntax. (#1212)

Other Changes

  • Add support for Python 3.15 (#1226)
  • [core] Add context manager support to Observer class. The observer can now be used with a with statement for automatic start/stop management. (#1090)
  • [core] Add support for the follow_symlink keyword argument to ObservedWatch. (#1086)
  • [core] Added the ignore_policy argument to PatternMatchingEventHandler and RegexMatchingEventHandler to configure multi-path event filtering (moves/renames). PatternMatchingEventHandler is now strict by default, aligning with RegexMatchingEventHandler. (#412, #423)
  • [core] Added the watchdog.utils.Seconds type alias and used it for the time-duration parameters (timeout, polling_interval, kill_after, ...) instead of documenting the unit in each docstring. Duration parameters previously hinted as int now accept float.
  • [core] Adjust Observer.schedule() path type annotation to reflect the pathlib.Path support. (#1096)
  • [core] Allow scheduling watches on individual files in Observer.schedule(). (#1034)
  • [core] Call task_done() for the stop sentinel in dispatch_events() to prevent join() from hanging. (#1159)
  • [core] case_sensitive=False matching now really ignores case on Python < 3.13. The PurePath.full_match() fallback compiled its regex without re.IGNORECASE, so only the patterns were lower-cased and a path such as FOO.PY never matched **/*.py. (#1263)
  • [core] dispatch_events() no longer re-adds a watch that unschedule() removed, which leaked one _handlers entry per watch that had an event in flight. (#1261)
  • [core] Do not retain an event handler when Observer.schedule() fails to create or start its emitter.
  • [core] EventEmitter and EventDispatcher reject a bool timeout. bool subclasses int, so timeout=True was stored and treated as 1.0 seconds. (#1287)
  • [core] Fixed generate_sub_moved_events() corrupting paths when the directory name appears multiple times in the path. (#1158)
  • [core] ObservedWatch equality now includes follow_symlink, so scheduling a path a second time with a different follow_symlink value no longer collapses onto the first watch and silently drops the request. (#1262)
  • [core] RegexMatchingEventHandler no longer matches its regexes against an empty destination path for events that are not moves. Since events became dataclasses, hasattr(event, "dest_path") is always true, so a regex matching the empty string (e.g. ^(?!.*\.pyc$).*$) let every event through, and such an ignore regex dropped every event. PatternMatchingEventHandler had the same check.
  • [core] remove_handler_for_watch() no longer re-adds a watch that unschedule() removed, which leaked one empty _handlers entry per call. (#1285)
  • [core] Add win_arm64 to the list of platform-specific wheels published to PyPI. (#1137)
  • [core] Add manylinux_2_17 to the list of platform-specific wheels published to PyPI. (#1125)
  • [inotify] Add support for the follow_symlink keyword argument. (#1086)
  • [inotify] Do not suppress registration errors for the requested root path. A missing root now raises FileNotFoundError from observer.start(), or from observer.schedule() when already running. Recursive descendant failures remain tolerated. (#1157)
  • [inotify] Keep watching newly created subdirectories when recursive watches filter out creation events. (#990)
  • [inotify] Reduce number of created inotify instance. (#1099)
  • [inotify] Snapshot the watch group before the blocking read in InotifyEmitter.queue_events() so stopping the emitter cannot raise AttributeError on a cleared self._inotify.
  • [fsevents] Added the latency keyword argument to FSEventsEmitter and FSEventsObserver (defaulting to watchdog.observers.fsevents.DEFAULT_FSEVENTS_LATENCY), exposing the FSEvents stream latency previously hard-coded at 10 ms. Raising it coalesces duplicate events. (#835)
  • [fsevents] Add support for the follow_symlink keyword argument. (#1086)
  • [fsevents] Support free-threading and give each emitter its own stream and run loop to prevent shutdown leaks. (#1140)
  • [fsevents] Use multi-phase initialization (PEP 489). (#1108)
  • [windows] A rename whose RENAMED_OLD and RENAMED_NEW records arrive in different get_events() batches no longer emits a move event with an empty src_path. (#1286)

... (truncated)

Changelog

Sourced from watchdog's changelog.

7.1.0


2026-11-04 • `full history <https://github.com/gorakhargosh/watchdog/compare/v7.0.0...v7.1.0>`__

Other Changes

  • [fsevents] Fix building the extension on PyPy 3.12 by updating the bundled pythoncapi_compat.h. ([#1397](https://github.com/gorakhargosh/watchdog/issues/1397) &lt;https://github.com/gorakhargosh/watchdog/issues/1397&gt;__)

  • [inotify] Create the inotify instance lazily so observer and polling imports succeed when the inotify instance limit is reached. ([#1389](https://github.com/gorakhargosh/watchdog/issues/1389) &lt;https://github.com/gorakhargosh/watchdog/issues/1389&gt;__)

  • [inotify] Reconcile recursively watched directories renamed before their source watch was registered, and simulate existing descendants so their initial changes are reported. ([#1383](https://github.com/gorakhargosh/watchdog/issues/1383) &lt;https://github.com/gorakhargosh/watchdog/pull/1383&gt;__)

  • [inotify] Reconcile recursive watches after the kernel reports an inotify queue overflow so subsequent filesystem changes are observed. ([#654](https://github.com/gorakhargosh/watchdog/issues/654) &lt;https://github.com/gorakhargosh/watchdog/pull/654&gt;__)

  • [inotify] Watch directories moved into a recursively watched directory from outside of it, so that changes inside them are reported. ([#1094](https://github.com/gorakhargosh/watchdog/issues/1094) &lt;https://github.com/gorakhargosh/watchdog/issues/1094&gt;__)

  • [inotify] Fix the inotify thread dying with a KeyError when a directory tree is copied or extracted into a recursively watched directory, which stopped all inotify observers in the process. ([#1388](https://github.com/gorakhargosh/watchdog/issues/1388) &lt;https://github.com/gorakhargosh/watchdog/pull/1388&gt;__)

  • [observers] Align BaseObserver with BaseThread by using on_thread_start() instead of overriding start(). ([#286](https://github.com/gorakhargosh/watchdog/issues/286) &lt;https://github.com/gorakhargosh/watchdog/issues/286&gt;__)

  • [watchmedo] Fix watchmedo generate-tricks-yaml output so that watchmedo tricks can load it: trick options are now nested under the trick name instead of under unsupported args/kwargs keys. ([#1403](https://github.com/gorakhargosh/watchdog/issues/1403) &lt;https://github.com/gorakhargosh/watchdog/pull/1403&gt;__)

  • Thanks to our beloved contributors: @​BoboTiG, @​prateek-dagar, @​monosans, @​taltal-beep, @​Aschenbath, @​yangfan-yf-yf, @​alexruperez, @​PDGGK, @​Skeletor-Pirate

7.0.0

2026-10-31 • full history <https://github.com/gorakhargosh/watchdog/compare/v6.0.0...v7.0.0>__

Breaking Changes

  • Drop support for Python 3.9 and 3.10.
  • [core] Changed pattern matching mechanism from using path.match() to path.full_match(). Users must update patterns to glob-like syntax: e.g., *.py to **/*.py. ([#1101](https://github.com/gorakhargosh/watchdog/issues/1101) <https://github.com/gorakhargosh/watchdog/pull/1101>__)
  • [core] Added FileAttribEvent and DirAttribEvent for file and directory metadata modifications (such as permissions or timestamps), separate from content modifications. These events no longer trigger on_modified(); implement on_attrib() to handle them. On Windows 10 (1709+) and Windows Server 2016+, ReadDirectoryChangesExW is used to differentiate attribute modifications, with fallback to ReadDirectoryChangesW on older versions or unsupported file shares. ([#260](https://github.com/gorakhargosh/watchdog/issues/260) <https://github.com/gorakhargosh/watchdog/issues/260>__)
  • [watchmedo] Changed the default --patterns value from "*" to "**", so the default matches absolute paths at any depth under the full_match() semantics introduced by #1101, and updated the CLI help text and docs to the **/ glob syntax. ([#1212](https://github.com/gorakhargosh/watchdog/issues/1212) <https://github.com/gorakhargosh/watchdog/issues/1212>__)

Other Changes

  • Add support for Python 3.15 ([#1226](https://github.com/gorakhargosh/watchdog/issues/1226) <https://github.com/gorakhargosh/watchdog/issues/1226>__)
  • [core] Add context manager support to Observer class. The observer can now be used with a with statement for automatic start/stop management. ([#1090](https://github.com/gorakhargosh/watchdog/issues/1090) <https://github.com/gorakhargosh/watchdog/pull/1149>__)
  • [core] Add support for the follow_symlink keyword argument to ObservedWatch. ([#1086](https://github.com/gorakhargosh/watchdog/issues/1086) <https://github.com/gorakhargosh/watchdog/pull/1086>__)
  • [core] Added the ignore_policy argument to PatternMatchingEventHandler and RegexMatchingEventHandler to configure multi-path event filtering (moves/renames). PatternMatchingEventHandler is now strict by default, aligning with RegexMatchingEventHandler. ([#412](https://github.com/gorakhargosh/watchdog/issues/412) <https://github.com/gorakhargosh/watchdog/issues/412>, [#423](https://github.com/gorakhargosh/watchdog/issues/423) <https://github.com/gorakhargosh/watchdog/issues/423>)
  • [core] Added the watchdog.utils.Seconds type alias and used it for the time-duration parameters (timeout, polling_interval, kill_after, ...) instead of documenting the unit in each docstring. Duration parameters previously hinted as int now accept float.
  • [core] Adjust Observer.schedule() path type annotation to reflect the pathlib.Path support. ([#1096](https://github.com/gorakhargosh/watchdog/issues/1096) <https://github.com/gorakhargosh/watchdog/pull/1096>__)
  • [core] Allow scheduling watches on individual files in Observer.schedule(). ([#1034](https://github.com/gorakhargosh/watchdog/issues/1034) <https://github.com/gorakhargosh/watchdog/issues/1034>__)
  • [core] Call task_done() for the stop sentinel in dispatch_events() to prevent join() from hanging. ([#1159](https://github.com/gorakhargosh/watchdog/issues/1159) <https://github.com/gorakhargosh/watchdog/pull/1159>__)
  • [core] case_sensitive=False matching now really ignores case on Python < 3.13. The PurePath.full_match() fallback compiled its regex without re.IGNORECASE, so only the patterns were lower-cased and a path such as FOO.PY never matched **/*.py. ([#1263](https://github.com/gorakhargosh/watchdog/issues/1263) <https://github.com/gorakhargosh/watchdog/pull/1263>__)
  • [core] dispatch_events() no longer re-adds a watch that unschedule() removed, which leaked one _handlers entry per watch that had an event in flight. ([#1261](https://github.com/gorakhargosh/watchdog/issues/1261) <https://github.com/gorakhargosh/watchdog/pull/1261>__)
  • [core] Do not retain an event handler when Observer.schedule() fails to create or start its emitter.
  • [core] EventEmitter and EventDispatcher reject a bool timeout. bool subclasses int, so timeout=True was stored and treated as 1.0 seconds. ([#1287](https://github.com/gorakhargosh/watchdog/issues/1287) <https://github.com/gorakhargosh/watchdog/pull/1287>__)
  • [core] Fixed generate_sub_moved_events() corrupting paths when the directory name appears multiple times in the path. ([#1158](https://github.com/gorakhargosh/watchdog/issues/1158) <https://github.com/gorakhargosh/watchdog/pull/1158>__)
  • [core] ObservedWatch equality now includes follow_symlink, so scheduling a path a second time with a different follow_symlink value no longer collapses onto the first watch and silently drops the request. ([#1262](https://github.com/gorakhargosh/watchdog/issues/1262) <https://github.com/gorakhargosh/watchdog/pull/1262>__)
  • [core] RegexMatchingEventHandler no longer matches its regexes against an empty destination path for events that are not moves. Since events became dataclasses, hasattr(event, "dest_path") is always true, so a regex matching the empty string (e.g. ^(?!.*\.pyc$).*$) let every event through, and such an ignore regex dropped every event. PatternMatchingEventHandler had the same check.
  • [core] remove_handler_for_watch() no longer re-adds a watch that unschedule() removed, which leaked one empty _handlers entry per call. ([#1285](https://github.com/gorakhargosh/watchdog/issues/1285) <https://github.com/gorakhargosh/watchdog/pull/1285>__)
  • [core] Add win_arm64 to the list of platform-specific wheels published to PyPI. ([#1137](https://github.com/gorakhargosh/watchdog/issues/1137) <https://github.com/gorakhargosh/watchdog/issues/1137>__)
  • [core] Add manylinux_2_17 to the list of platform-specific wheels published to PyPI. ([#1125](https://github.com/gorakhargosh/watchdog/issues/1125) <https://github.com/gorakhargosh/watchdog/issues/1125>__)

... (truncated)

Commits
  • b5274bf feat: version v7.1.0 [skip ci] (#1404)
  • e0994bd docs: add @​taltal-beep to contributors [skip ci] (#1405)
  • d481d1c fix(watchmedo): make generate-tricks-yaml output loadable by watchmedo tricks...
  • 5236a9a fix(inotify): create the inotify instance lazily (#1390)
  • 3d8a07a ci: enable PyPy 3.11 testing and PyPy 3.11/3.12 wheel builds on macOS (#1400)
  • 103ca34 docs: add @​monosans to contributors [skip ci] (#1401)
  • c7c09c6 fix(fsevents): update pythoncapi_compat.h to fix the PyPy 3.12 build (#1398)
  • 68f8321 chore(deps): bump mypy from 2.4.0 to 2.4.1 (#19)
  • 235c832 chore(deps): bump types-pyyaml from 6.0.12.20260906 to 6.0.12.20261030 (#18)
  • dbb57f6 chore(deps): bump pytest from 9.1.1 to 9.2.0 (#17)
  • Additional commits viewable in compare view

Updates python-dateutil from 2.9.0.post0 to 4.0.0

Release notes

Sourced from python-dateutil's releases.

4.0.0

dateutil 4.0 requires Python 3.11 or later and no longer depends on six. Apart from that, the changes in this release are bug fixes, but note that isoparse is now stricter about the numeric fields it accepts (see below).

Deprecations

  • Dropped support for Python versions older than 3.11 and removed the dependency on six, along with Python 2 compatibility helpers that were never part of the public API, such as dateutil.tz.tzname_in_python2. (gh pr #1625)

Bugfixes

  • parser.isoparse, and the isoparser methods parse_isodate, parse_isotime and parse_tzstr, now require each numeric field to be exactly the expected number of ASCII digits. Strings that were previously accepted, such as 20200728121240 (read as 21:24), 2014- 4-21 and 2_14-04-21, and offsets such as +-1:00, now raise ValueError. tzical applies the same check to TZOFFSETFROM and TZOFFSETTO. Reported by @​janos-gonye (gh issue #1074). Fixed by @​varun3257 (gh pr #1617).
  • Fixed an issue where iterating over a cached rrule or rruleset could hang forever if another iterator over the same rule had already completed the cache, for example when a cached rrule was included twice in an rruleset. Reported by @​bysiber (gh pr #1455). Fixed by @​pganssle (gh pr #1655).
  • Unpickling a tzutc now gives the dateutil.tz.UTC singleton, and unpickling a tzoffset gives the same object as calling tzoffset(name, offset). Previously unpickling bypassed the singleton-generation logic. Reported and fixed by @​masipcat (gh issue #1051, gh pr #1053).
  • relativedelta(yearday=366) now resolves to December 31 in leap years. Previously it gave December 30, the same date as yearday=365. Reported and fixed by @​Master-Norna (gh pr #1583).

Misc

  • The build backend is now Hatchling, and the package metadata is in pyproject.toml. Versions are still derived from Git tags and exposed as dateutil.__version__. This mainly affects people building dateutil from source. (gh pr #1637, #1638)
  • Changes to CI, tests and release tooling that do not affect users of the package: gh pr #1636, #1644, #1645, #1646, #1648, #1649, #1650.

3.0.0

This is the last major version of dateutil that will support any version of Python older than 3.11. The next release will be the 4.x series, which will support Python 3.11 and later. We may release fixes for serious bugs in the 3.0.x series, but there are no plans for new features there.

The biggest change in this release is a rewrite of tz.tzfile, which affects nearly every user of dateutil.tz and changes the UTC offset of nonexistent times (see below). dateutil also now depends on the tzdata package, and no longer ships its own time zone database.

Data updates

  • dateutil no longer bundles a copy of the IANA time zone database. Time zone data now comes from the system (see dateutil.tz.TZPATH) or, failing that, from the new tzdata dependency, so the data version is whatever version of tzdata is installed. (gh pr #1130)

Features

  • Rewrote tz.tzfile based on a backport of the zoneinfo module's pure-Python implementation. This adds support for Version 2 and Version 3 tzfile(5) binaries, resolving issues with timestamps beyond 2038 and "slim" format binaries. (gh issues #462, #1059, gh pr #1130)
  • Added dateutil.tz.TZPATH and dateutil.tz.reset_tzpath to allow for runtime configuration of the IANA time zone data search path. These replace the mutable dateutil.tz.TZPATHS list, which has been removed. (gh pr #1130)
  • dateutil now depends on the tzdata package, which gettz consults after the search path and before the Windows registry. On Windows this means that names that are both IANA keys and Windows time zone names, such as "UTC", now return a tzfile rather than a tzwin. (gh pr #1130)

Bugfixes

  • tz.tzfile now follows PEP 495 for times that fall in a gap: with fold=0 it uses the offset from before the transition, and with fold=1 the offset from after it. Previously it always used the offset from after the transition, so for example datetime(2003, 4, 6, 2, 30, tzinfo=tz.gettz("America/New_York")) had a UTC offset of -04:00, where it now has -05:00, the same as with zoneinfo. (gh pr #1130)
  • tz.tzfile objects for fixed-offset zones, such as tz.gettz("UTC"), now return their offset, DST offset and abbreviation when utcoffset, dst and tzname are called with None, as tz.tzutc, tz.tzoffset and zoneinfo.ZoneInfo do. This means that datetime.time objects with such a zone attached are now aware: time(12, tzinfo=tz.gettz("UTC")).isoformat() is now "12:00:00+00:00" rather than "12:00:00". (gh pr #1130)
  • tz.tzfile now infers dst() from the standard time on both sides of each DST period, rather than only the one before it, and does so for each transition rather than for each local time type. This fixes dst() for double summer time (e.g. in Europe/London in the 1940s), for half-hour DST (e.g. in Pacific/Rarotonga) and where the standard offset changed at the same time as a DST transition (e.g. in America/Bahia_Banderas in 2010). Against the standard offsets in the tz database source, the only remaining errors are in Europe/Paris in 1944 and 1945. (gh pr #1130)
  • Fixed rrulestr raising ValueError on experimental X- parameters in an RRULE line (such as GNOME Evolution's X-EVOLUTION-ENDDATE); these are now ignored as RFC 5545 permits. Fixed by @​yajo (gh pr #1374)
  • Enabled pickling and deepcopy of cached rrule and rruleset instances. The cache setting is preserved, and cached results are regenerated on demand without copying locks or generators. Reported by @​niccokunzmann (gh issue #1369). Fixed by @​Jay1023CN (gh pr #1600).
  • Fixed relativedelta.__ne__ raising TypeError when comparing against an unsupported type such as None; it now returns True. Reported and fixed by @​kevinkt1 (gh issue #1157, gh pr #1158)
  • Raised the minimum version of six to 1.6, fixing No module named 'six.moves' errors with older versions. Reported by @​skytreader (gh issue #1415), fixed by @​jdarias3 (gh pr #1424).

Deprecations

  • Deprecated the dateutil.zoneinfo module. The module now acts as a wrapper around the tzdata package and will be removed in a future version. Users are encouraged to migrate to dateutil.tz.gettz or the standard library's zoneinfo module. dateutil.zoneinfo.rebuild.rebuild no longer does anything, and by default raises RebuildDeprecationWarning as an error; filter the warning to call it as a no-op. (gh pr #1130)
  • Deprecated passing gettz a relative key that refers to a file outside of every directory on TZPATH, such as "../../etc/localtime". By default this now raises dateutil.tz.DeprecatedTzKeyWarning as an error; filter the warning to keep the old behavior for now, or pass an absolute path instead. (gh pr #1130)

Documentation changes

... (truncated)

Changelog

Sourced from python-dateutil's changelog.

Version 4.0.0 (2026-11-01)

dateutil 4.0 requires Python 3.11 or later and no longer depends on six. Apart from that, the changes in this release are bug fixes, but note that isoparse is now stricter about the numeric fields it accepts (see below).

Deprecations

  • Dropped support for Python versions older than 3.11 and removed the dependency on six, along with Python 2 compatibility helpers that were never part of the public API, such as dateutil.tz.tzname_in_python2. (gh pr #1625)

Bugfixes

  • parser.isoparse, and the isoparser methods parse_isodate, parse_isotime and parse_tzstr, now require each numeric field to be exactly the expected number of ASCII digits. Strings that were previously accepted, such as 20200728121240 (read as 21:24), 2014- 4-21 and 2_14-04-21, and offsets such as +-1:00, now raise ValueError. tzical applies the same check to TZOFFSETFROM and TZOFFSETTO. Reported by @​janos-gonye (gh issue #1074). Fixed by @​varun3257 (gh pr #1617).
  • Fixed an issue where iterating over a cached rrule or rruleset could hang forever if another iterator over the same rule had already completed the cache, for example when a cached rrule was included twice in an rruleset. Reported by @​bysiber (gh pr #1455). Fixed by @​pganssle (gh pr #1655).
  • Unpickling a tzutc now gives the dateutil.tz.UTC singleton, and unpickling a tzoffset gives the same object as calling tzoffset(name, offset). Previously unpickling bypassed the singleton-generation logic. Reported and fixed by @​masipcat (gh issue #1051, gh pr #1053).
  • relativedelta(yearday=366) now resolves to December 31 in leap years. Previously it gave December 30, the same date as yearday=365. Reported and fixed by @​Master-Norna (gh pr #1583).

Misc

  • The build backend is now Hatchling, and the package metadata is in pyproject.toml. Versions are still derived from Git tags and exposed as dateutil.__version__. This mainly affects people building dateutil from source. (gh pr #1637, #1638)
  • Changes to CI, tests and release tooling that do not affect users of the

... (truncated)

Commits
  • a78cbd8 Prepare release 4.0.0
  • d23ff76 Fix yearday=366 resolving to Dec 30 in leap years
  • 5391455 Return the cached instances when unpickling tzutc and tzoffset
  • 6f13622 Reject non-digit characters in isoparse and tzical numeric fields
  • 6e1864c Release the rrule cache lock on every exit from a refill (#1655)
  • 71d92da Skip coverage collection on PyPy in CI
  • d9cad2f Run the tests in parallel with pytest-xdist (#1649)
  • 433c98b Add news fragment for #1650
  • ea6bc3f Remove stale warning from the tz tox environments
  • 27ecba2 Keep GitHub Actions pins updated with Dependabot
  • Additional commits viewable in compare view

Updates streamlit from 1.66.1 to 1.67.0

Release notes

Sourced from streamlit's releases.

1.67.0

What's Changed

New Features 🎉

Bug Fixes 🐛

... (truncated)

Commits
  • 89f84a3 Up version to 1.67.0
  • b44ea24 [fix] Label ECharts tooltip fields for dataframe sources (#17883)
  • 0199288 [fix] Better ECharts layout for titles, treemaps, and markLines (#17885)
  • 49ae4fe [fix] Name the offending value in ECharts serialization errors (#17881)
  • 23c01ce [fix] Let the page scroll over ECharts treemaps and roam charts (#17882)
  • 47ce6ce [docs] Clarify agent API tool text from live evaluations (#17880)
  • c6218b9 [fix] Keep stretch dataframes inside their parent on resize (#17879)
  • 0caf2fa [chore] AI-assisted frontend test coverage improvements (#17876)
  • 9213d6b [feature] Add st.grid for responsive grid layouts (#17800)
  • 0408177 [fix] Handle script_finished for the run it names (#17686)
  • Additional commits viewable in compare view

Updates pandas from 3.0.6 to 3.1.1

Release notes

Sourced from pandas's releases.

pandas 3.1.1

We are pleased to announce the release of pandas 3.1.1. This is a patch release in the 3.1.x series and includes some regression fixes and bug fixes. We recommend that all users of the 3.1.x series upgrade to this version.

See the full whatsnew for a list of all the changes.

The release can be installed from PyPI:

python -m pip install --upgrade pandas==3.1.*

Or from conda-forge

conda install -c conda-forge pandas=3.1

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

pandas 3.1.0

We are pleased to announce the release of pandas 3.1.0. This release includes some new features, bug fixes, and performance improvements. We recommend that all users upgrade to this version.

Highlights include:

See the detailed release notes for a list of all the changes.

The release can be installed from PyPI:

python -m pip install --upgrade pandas

Or from conda-forge

conda install -c conda-forge pandas

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

pandas 3.1.0rc0

We are pleased to announce a release candidate for pandas 3.1.0.

See the whatsnew for a list of all the changes.

The release can be installed from PyPI:

python -m pip install --upgrade --pre pandas==3.1.0rc0

... (truncated)

Commits
  • 3dcc6fb RLS: 3.1.1
  • 01560e3 Backport PR #71896 on branch 3.1.x (DOC: cleanup 3.1.1 whatsnew) (#71898)
  • 49709c4 [backport 3.1.x] BUG: ffill/bfill on Arrow arrays without NA returns a view o...
  • 55089f8 Backport PR #71025 on branch 3.1.x (BUG: \s and \S in str regex methods missi...
  • eea23d0 Backport PR #71782 on branch 3.1.x (BUG: py.path.local treated as an open buf...
  • e427eb5 [backport 3.1.x] DOC: avoid system-ui in default font-family for the docs (re...
  • 3120a57 Backport PR #71572 on branch 3.1.x (BLD: don't include moments_simd.hpp in mo...
  • 378620e Backport PR #71865 on branch 3.1.x (REGR: ensure map() with datetime-like dty...
  • ceca8cb Backport PR #71495 on branch 3.1.x (BUG: support python-dateutil 3.0 tzfile (...
  • 68fc76e Backport PR #71661 on branch 3.1.x (CI: Remove install requirement-dev.txt sm...
  • Additional commits viewable in compare view

Updates pytest from 9.1.1 to 9.2.0

Release notes

Sourced from pytest's releases.

9.2.0

pytest 9.2.0 (2026-10-27)

Removals and backward incompatible breaking changes

  • #14716: -c now raises a usage error for a path that does not exist, is a directory, or is in a format pytest has no loader for. Such paths were previously either ignored or reported as an unhandled FileNotFoundError.

  • #8593: The indirect, ids and scope arguments of Metafunc.parametrize() <pytest.Metafunc.parametrize> -- and therefore of @pytest.mark.parametrize <pytest.mark.parametrize ref> -- are now keyword-only.

    Passing them positionally was a common source of confusing errors, e.g. parametrize("arg1", "arg2", [(1, 2)]) made the argvalues land in indirect and failed with indirect fixture '(1, 2)' doesn't exist; such mistakes now fail with an understandable TypeError. The type annotations have always declared these arguments as keyword-only.

  • #993: Plugin import failures at startup are now reported and classified instead of escaping as a raw tra...

    Description has been truncated

Bumps the python-packages group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [watchdog](https://github.com/gorakhargosh/watchdog) | `6.0.0` | `7.1.0` |
| [python-dateutil](https://github.com/dateutil/dateutil) | `2.9.0.post0` | `4.0.0` |
| [streamlit](https://github.com/streamlit/streamlit) | `1.66.1` | `1.67.0` |
| [pandas](https://github.com/pandas-dev/pandas) | `3.0.6` | `3.1.1` |
| [pytest](https://github.com/pytest-dev/pytest) | `9.1.1` | `9.2.0` |



Updates `watchdog` from 6.0.0 to 7.1.0
- [Release notes](https://github.com/gorakhargosh/watchdog/releases)
- [Changelog](https://github.com/gorakhargosh/watchdog/blob/master/changelog.rst)
- [Commits](gorakhargosh/watchdog@v6.0.0...v7.1.0)

Updates `python-dateutil` from 2.9.0.post0 to 4.0.0
- [Release notes](https://github.com/dateutil/dateutil/releases)
- [Changelog](https://github.com/dateutil/dateutil/blob/master/NEWS)
- [Commits](dateutil/dateutil@2.9.0.post0...4.0.0)

Updates `streamlit` from 1.66.1 to 1.67.0
- [Release notes](https://github.com/streamlit/streamlit/releases)
- [Commits](streamlit/streamlit@1.66.1...1.67.0)

Updates `pandas` from 3.0.6 to 3.1.1
- [Release notes](https://github.com/pandas-dev/pandas/releases)
- [Commits](pandas-dev/pandas@v3.0.6...v3.1.1)

Updates `pytest` from 9.1.1 to 9.2.0
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@9.1.1...9.2.0)

---
updated-dependencies:
- dependency-name: watchdog
  dependency-version: 7.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: python-packages
- dependency-name: python-dateutil
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: python-packages
- dependency-name: streamlit
  dependency-version: 1.67.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-packages
- dependency-name: pandas
  dependency-version: 3.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-packages
- dependency-name: pytest
  dependency-version: 9.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: python-packages
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Nov 13, 2026
@coderabbitai

coderabbitai Bot commented Nov 13, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 82b34e0d-c82f-4bb5-814d-c75ca2e076f2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants