Python Requirements Update

[edx-requirements-bot]

Python requirements update. Please review the changelogs for the upgraded packages.

[edx-requirements-bot]

List of packages in the PR without any issue.

• babel changes from 2.13.0 to 2.13.1
• boto3 changes from 1.28.62 to 1.28.72
• botocore changes from 1.31.62 to 1.31.72
• charset-normalizer changes from 3.3.0 to 3.3.1
• cryptography changes from 41.0.4 to 41.0.5
• django-cors-headers changes from 4.2.0 to 4.3.0
• django-mysql changes from 4.11.0 to 4.12.0
• edx-drf-extensions changes from 8.10.0 to 8.12.0
• edx-lint changes from 5.3.4 to 5.3.6
• edx-rest-api-client changes from 5.6.0 to 5.6.1
• faker changes from 19.7.0 to 19.12.0
• greenlet changes from 3.0.0 to 3.0.1
• moto changes from 4.2.5 to 4.2.6
• pip changes from 23.2.1 to 23.3.1
• psutil changes from 5.9.5 to 5.9.6
• pycodestyle changes from 2.11.0 to 2.11.1
• pydata-sphinx-theme changes from 0.14.1 to 0.14.2
• pylint-django changes from 2.5.3 to 2.5.5
• pytest changes from 7.4.2 to 7.4.3
• ruamel-yaml changes from 0.17.35 to 0.18.2
• urllib3 changes from 1.26.17 to 1.26.18
• virtualenv changes from 20.24.5 to 20.24.6
• werkzeug changes from 3.0.0 to 3.0.1

[edx-requirements-bot]

These Packages need manual review..

• [MAJOR] astroid changes from 2.15.8 to 3.0.1
• [REMOVED] lazy-object-proxy (1.9.0) removed from the requirements
• [MAJOR] pylint changes from 2.17.7 to 3.0.2
• [REMOVED] wrapt (1.13.3) removed from the requirements

[MichaelRoytman]

@zubairshakoorarbisoft Can you explain why this pull request was merged, please? There is a test failure on this pull request, and I would have preferred that this pull request not have been merged without resolution of the test failure or at least a message sent to our team.

We get alerted on a weekly basis about these Python requirements upgrades, and I've noticed members outside of the owning team frequently merge these pull requests before we can review them. Can you share any context about why that is happening? If you need requirements merged faster than we are doing them, I'd like to know. It feels redundant to have two teams monitoring these updates, so I'd like to make sure only one team feels responsible.

Thank you.

[zubairshakoorarbisoft]

Yes @MichaelRoytman Sure! Actually I created this PR for one of my branch to have latest requirements. I merged this PR into my branch not in master.
Here is my PR which is still not merged due to test failure, there is a flakey test we need to fix it.

[MichaelRoytman]

Hi, @zubairshakoorarbisoft. Thanks for the update. My mistake! I apologize for that.

We have a ticket on our board to fix the test. I hope we can get to it soon.