Skip to content
Open
Changes from all commits
Commits
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
6 changes: 3 additions & 3 deletions requirements.txt
Original file line number Diff line number Diff line change
Expand Up @@ -483,9 +483,9 @@ pyasn1-modules==0.4.2 \
--hash=sha256:29253a9207ce32b64c3ac6600edc75368f98473906e8fd1043bd6b5b1de2c14a \
--hash=sha256:677091de870a80aae844b1ca6134f54652fa2c8c5a52aa396440ac3106e941e6
# via google-auth
pyparsing==3.2.5 \
--hash=sha256:2df8d5b7b2802ef88e8d016a2eb9c7aeaa923529cd251ed0fe4608275d4105b6 \
--hash=sha256:e38a4f02064cf41fe6593d328d0512495ad1f3d8a91c4f73fc401b3079a59a5e
pyparsing==3.3.2 \
--hash=sha256:850ba148bd908d7e2411587e247a1e4f0327839c40e2e5e6d05a007ecc69911d \
--hash=sha256:c777f4d763f140633dcb6d8a3eda953bf7a214dc4eff598413c070bcdc117cbc
Comment on lines +486 to +488

Choose a reason for hiding this comment

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

medium

The update to pyparsing==3.3.2 includes changes from v3.3.0 where DeprecationWarnings are now emitted for non-PEP8 compliant method names. While this is a minor version bump, it's important to check if any existing code uses these deprecated names. The pyparsing release notes mention a utility (pyparsing.tools.cvt_pyparsing_pep8_names.py) that can help in migrating to the new names, which would be beneficial for long-term maintainability and to prevent warnings in logs.

# via -r requirements.in
pyproject-hooks==1.2.0 \
--hash=sha256:1e859bd5c40fae9448642dd871adf459e5e2084186e8d2c2a79a824c970da1f8 \
Expand Down