Bump the pip group with 5 updates

[dependabot]

Bumps the pip group with 5 updates:

Package	From	To
faker	29.0.0	30.0.0
prompt-toolkit	3.0.47	3.0.48
redis	5.0.8	5.1.0
tzdata	2024.1	2024.2
virtualenv	20.26.5	20.26.6

Updates faker from 29.0.0 to 30.0.0

Release notes

Sourced from faker's releases.

Release v30.0.0

See CHANGELOG.md.

Changelog

Sourced from faker's changelog.

v30.0.0 - 2024-09-25

• Force the slug always be generated with ASCII characters. Thanks @​Pandede.

Commits

• 3dc6de2 Bump version: 29.0.0 → 30.0.0
• 20f9a96 📝 Update CHANGELOG.md
• 8aa0f07 Force the slug always be generated with ASCII characters (#2104)
• See full diff in compare view

Updates prompt-toolkit from 3.0.47 to 3.0.48

Release notes

Sourced from prompt-toolkit's releases.

3.0.48

Fixes:

• Typing improvements:
  • Add @overload to contrib.regular_languages.compiler.Variables.get.
  • Use Sequence instead of list for words argument in completers.
• Improve ModalCursorShapeConfig:
  • Display an "underscore" cursor in Vi's "replace single" mode, like "replace" mode.
  • Display an "beam" cursor in Emacs (insert) mode.

Changelog

Sourced from prompt-toolkit's changelog.

3.0.48: 2024-09-25

Fixes:

• Typing improvements:
  • Add @overload to contrib.regular_languages.compiler.Variables.get.
  • Use Sequence instead of list for words argument in completers.
• Improve ModalCursorShapeConfig:
  • Display an "underscore" cursor in Vi's "replace single" mode, like "replace" mode.
  • Display an "beam" cursor in Emacs (insert) mode.

Commits

• 435bd99 Release 3.0.48
• ae1d635 Fixup for previous cursorshapes commit (#1900). (#1920)
• df4e244 Update type definition for words argument in completers (#1889)
• 728983b Improve ModalCursorShapeConfig for various input modes (#1900)
• 75615b1 Add @​overload to contrib.regular_languages.compiler.Variables.get
• See full diff in compare view

Updates redis from 5.0.8 to 5.1.0

Release notes

Sourced from redis's releases.

5.1.0

Changes

🚀 New Features

• Client-side caching (#3350, #3110, #3102, #3099, #3089, #3038)

How to start with Client-side caching?

1. Install redis-py 5.1.0
2. Use the following code snippet:

r = Redis(protocol=3, cache_config=CacheConfig())
cache = r.get_cache()
r.set("foo", "bar")
get key from redis and save in local cache
print(r.get("foo"))
get key from local cache
print(cache.get(CacheKey(command="GET", redis_keys=("foo",))).cache_value)
change key in redis (cause invalidation)
r.set("foo", "barbar")
Retrieves a new value from server and cache it
print(r.get("foo"))
Make sure that new value was cached
print(cache.get(CacheKey(command="GET", redis_keys=("foo",))).cache_value)

Check documentation to get more examples

🔥 Breaking Changes

• Timeseries insertion filters for close samples (#3228)
• Enhanced classes string representation (#3001)
• Partial clean up of Python 3.7 compatibility (#2928)

🐛 Bug Fixes

• Handle RESP3 sets as Python lists (#3324)
• Prevent async ClusterPipeline instances from becoming "false-y" (#3068)
• Add hostname field to _parse_node_line (#3343)
• More docs fixes (#3326)
• Delete the first-defined (and thus "duplicate") Script class (#3333)
• Catch a known DeprecationWarning when calling .close() (#3335)
• Add missed redismod at test_commands.py (#3369)

🧰 Maintenance

• Update README.md - mentioning redis 7.4 support (#3375)
• Update PyPy 3.8 to 3.10 in CI (#3370)
• Updated commands from docker-compose to docker compose (#3352)
• Added version restrictions for pytest-asyncio (#3362)

... (truncated)

Commits

• 7215a52 Updated package version (#3389)
• 2e46613 Client side caching refactoring (#3350)
• 7d73d74 DOC-4197: add TCEs to the geospatial query page (#3378)
• c7483b3 DOC-4196: add TCEs to the full-text query page (#3377)
• 64d4bb8 DOC-4194: add TCEs to the range query page (#3374)
• 0c8a986 DOC-4194: add TCEs to the exact match query page (#3372)
• cbb129d Update README.md - mentioning redis 7.4 support (#3375)
• 2fb40c1 TCEs for select command pages (#3361)
• e00f3d2 Add missed redismod at test_commands.py (#3369)
• 6c94faa Update PyPy 3.8 to 3.10 in CI (#3370)
• Additional commits viewable in compare view

Updates tzdata from 2024.1 to 2024.2

Release notes

Sourced from tzdata's releases.

2024.2: Release of upstream tzdata 2024b

Version 2024.2

Upstream version 2024b released 2024-09-04T19:27:47+00:00

Briefly:

Improve historical data for Mexico, Mongolia, and Portugal. System V names are now obsolescent. The main data form now uses %z. The code now conforms to RFC 8536 for early timestamps. Support POSIX.1-2024, which removes asctime_r and ctime_r. Assume POSIX.2-1992 or later for shell scripts. SUPPORT_C89 now defaults to 1.

Changes to past timestamps

Asia/Choibalsan is now an alias for Asia/Ulaanbaatar rather than being a separate Zone with differing behavior before April 2008. This seems better given our wildly conflicting information about Mongolia's time zone history. (Thanks to Heitor David Pinto.)

Historical transitions for Mexico have been updated based on official Mexican decrees. The affected timestamps occur during the years 1921-1927, 1931, 1945, 1949-1970, and 1981-1997. The affected zones are America/Bahia_Banderas, America/Cancun, America/Chihuahua, America/Ciudad_Juarez, America/Hermosillo, America/Mazatlan, America/Merida, America/Mexico_City, America/Monterrey, America/Ojinaga, and America/Tijuana. (Thanks to Heitor David Pinto.)

Historical transitions for Portugal, represented by Europe/Lisbon, Atlantic/Azores, and Atlantic/Madeira, have been updated based on a close reading of old Portuguese legislation, replacing previous data mainly originating from Whitman and Shanks & Pottenger. These changes affect a few transitions in 1917-1921, 1924, and 1940 throughout these regions by a few hours or days, and various timestamps between 1977 and 1993 depending on the region. In particular, the Azores and Madeira did not observe DST from 1977 to 1981. Additionally, the adoption of standard zonal time in former Portuguese colonies have been adjusted: Africa/Maputo in 1909, and Asia/Dili by 22 minutes at the start of 1912. (Thanks to Tim Parenti.)

Changes to past tm_isdst flags

The period from 1966-04-03 through 1966-10-02 in Portugal is now modeled as DST, to more closely reflect how contemporaneous changes in law entered into force.

Changes to data

Names present only for compatibility with UNIX System V (last released in the 1990s) have been moved to 'backward'. These names, which for post-1970 timestamps mostly just duplicate data of geographical names, were confusing downstream uses. Names moved to 'backward' are now links to geographical names. This affects behavior for TZ='EET' for some pre-1981 timestamps, for TZ='CET' for some pre-1947 timestamps, and for TZ='WET' for some pre-1996 timestamps.

... (truncated)

Changelog

Sourced from tzdata's changelog.

Version 2024.2

Upstream version 2024b released 2024-09-04T19:27:47+00:00

Briefly:

Improve historical data for Mexico, Mongolia, and Portugal. System V names are now obsolescent. The main data form now uses %z. The code now conforms to RFC 8536 for early timestamps. Support POSIX.1-2024, which removes asctime_r and ctime_r. Assume POSIX.2-1992 or later for shell scripts. SUPPORT_C89 now defaults to 1.

Changes to past timestamps

Asia/Choibalsan is now an alias for Asia/Ulaanbaatar rather than being a separate Zone with differing behavior before April 2008. This seems better given our wildly conflicting information about Mongolia's time zone history. (Thanks to Heitor David Pinto.)

Historical transitions for Mexico have been updated based on official Mexican decrees. The affected timestamps occur during the years 1921-1927, 1931, 1945, 1949-1970, and 1981-1997. The affected zones are America/Bahia_Banderas, America/Cancun, America/Chihuahua, America/Ciudad_Juarez, America/Hermosillo, America/Mazatlan, America/Merida, America/Mexico_City, America/Monterrey, America/Ojinaga, and America/Tijuana. (Thanks to Heitor David Pinto.)

Historical transitions for Portugal, represented by Europe/Lisbon, Atlantic/Azores, and Atlantic/Madeira, have been updated based on a close reading of old Portuguese legislation, replacing previous data mainly originating from Whitman and Shanks & Pottenger. These changes affect a few transitions in 1917-1921, 1924, and 1940 throughout these regions by a few hours or days, and various timestamps between 1977 and 1993 depending on the region. In particular, the Azores and Madeira did not observe DST from 1977 to 1981. Additionally, the adoption of standard zonal time in former Portuguese colonies have been adjusted: Africa/Maputo in 1909, and Asia/Dili by 22 minutes at the start of 1912. (Thanks to Tim Parenti.)

Changes to past tm_isdst flags

The period from 1966-04-03 through 1966-10-02 in Portugal is now modeled as DST, to more closely reflect how contemporaneous changes in law entered into force.

Changes to data

Names present only for compatibility with UNIX System V (last released in the 1990s) have been moved to 'backward'. These names, which for post-1970 timestamps mostly just duplicate data of geographical names, were confusing downstream uses. Names moved to 'backward' are now links to geographical names. This affects behavior for TZ='EET' for some pre-1981 timestamps, for TZ='CET' for some pre-1947 timestamps, and for TZ='WET' for some pre-1996 timestamps. Also, TZ='MET' now behaves like TZ='CET' and so uses the abbreviation "CET"

... (truncated)

Commits

• 0c324fb Update tzdata to 2024b
• 3986b28 Remove POSIXRULES= from make invocation
• aeeb380 Drop 3.6 and 3.7 to support Matrix
• 4cbaad2 Add support for Python 3.13
• See full diff in compare view

Updates virtualenv from 20.26.5 to 20.26.6

Changelog

Sourced from virtualenv's changelog.

v20.26.6 (2024-09-27)

Bugfixes - 20.26.6

- Properly quote string placeholders in activation script templates to mitigate
  potential command injection - by :user:`y5c4l3`. (:issue:`2768`)

Commits

• ec04726 release 20.26.6
• 86ddded Fix #2768: Quote template strings in activation scripts (#2771)
• 6bb3f62 [pre-commit.ci] pre-commit autoupdate (#2769)
• 220d49c Bump pypa/gh-action-pypi-publish from 1.10.1 to 1.10.2 (#2767)
• cf340c8 Merge pull request #2766 from pypa/release-20.26.5
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[coveralls]

Pull Request Test Coverage Report for Build 11097603205

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 80.916%

---

Totals
Change from base Build 11008633122:	0.0%
Covered Lines:	1255
Relevant Lines:	1551

---

💛 - Coveralls