build: add support for Python 3.12

[UsamaSadiq]

Description

• Creating PR to add support for Python 3.12 under the issue Drop Python 3.8 & Add Support for Python 3.12 #35457

[openedx-webhooks]

Thanks for the pull request, @UsamaSadiq!

This repository is currently maintained by @openedx/wg-maintenance-edx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[feanil]

Changes generally look good, just a couple of things to cleanup and then this will be good to land!

[kdmccormick]

@feanil @UsamaSadiq Looks like we're almost able to merge this. Any objections to backporting to Ulmo once it's in, so that Ulmo can simultaneously support both 3.11 and 3.12?

[UsamaSadiq]

@feanil @UsamaSadiq Looks like we're almost able to merge this. Any objections to backporting to Ulmo once it's in, so that Ulmo can simultaneously support both 3.11 and 3.12?

Yes, this PR will be ready to be merged soon. There shouldn't be any issue backporting it since it is only a support PR.

[feanil]

@UsamaSadiq I think I'm just waiting for you to address the few comments I had and then I can approve this to merge. Feel free to re-tag me for review when this PR is ready again.

[UsamaSadiq]

@UsamaSadiq I think I'm just waiting for you to address the few comments I had and then I can approve this to merge. Feel free to re-tag me for review when this PR is ready again.

@feanil I was away for 2 weeks. Will update this PR within this week, IA.

[farhan]

@UsamaSadiq Shouldn't we pass the test cases first?

[UsamaSadiq]

@farhan CI was green at first but tests failed after I made some changes. I'll fix the tests and then tag for review again.

@UsamaSadiq Shouldn't we pass the test cases first?

[UsamaSadiq]

@feanil edx-submissions version bump ( XQueue DEPR related changes ) was causing the test failures. I've reverted the package version bump from this PR for now. PR #37528 has the fix for the related test failure. I'll add a version constraint in the repository in a follow up PR which will be removed by the above mentioned PR to handle this as requirements upgrade PR is also failing tests due to the new package version.

Let's have this PR merged as soon as possible to avoid the need of rebasing or resolving conflicts again.