Chore!: Updating for Python 3.12

[Colin-Fredericks]

This addresses items from #109 and #120.

Overview:

• Lots of package version updates.
• Dropped Python 3.8, skipped straight over 3.9 and 3.10. Now supporting 3.11 and 3.12.
• Told pylint that it's ok when certain functions have lots of inputs.
• Started improvements to the ReadMe.

BREAKING CHANGE: Python 3.8 no longer supported. This commit by itself doesn't do that, but odds are good that some of the package updates do.

Thank you to Feanil for the help!

[openedx-webhooks]

Thanks for the pull request, @Colin-Fredericks!

What's next?

Please work through the following steps to get your changes 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.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/openedx-unmaintained. Tag them in a comment and let them know that your changes are ready for review.

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]

@Colin-Fredericks looks like there is a confilict, I think you need to rebase your local master on top of the openedx:master

[Colin-Fredericks]

How's that?

[Colin-Fredericks]

I'm not 100% sure why the 3.8 tests went away from the workflow but there's no 3.12 test. Sort of expected that to appear automatically I guess. 🤷

[feanil]

Since you haven't committed here before, the test runs have to be approved, and so it lists the pending set of required tests and doesn't run all the tests. I've approved it and both the 3.11 and 3.12 test have run. It looks like the conventional commits check is failing. Sorry for not mentioning that we use conventional commits on all the code repos now. Can you update the commit messages to use the conventional commits structure?

[Colin-Fredericks]

Since you haven't committed here before, the test runs have to be approved, and so it lists the pending set of required tests and doesn't run all the tests. I've approved it and both the 3.11 and 3.12 test have run. It looks like the conventional commits check is failing. Sorry for not mentioning that we use conventional commits on all the code repos now. Can you update the commit messages to use the conventional commits structure?

Ah, ok. I think I found an older version of the commit guidelines. Will edit.

Edit: Oh, wait, that's what happened - I saw these commit guidelines and read them as "how to write a pull request" instead of "how to write a commit message". Fixing.

[Colin-Fredericks]

Sigh. Revising old commits is apparently a nightmare, and I can't squash this set of commits. It may be worth me just erasing this pull request, redoing the commits from the ground up, and making a new pull request.

[feanil]

You should be able to do an interactive rebase and just re-word the commits: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History#_changing_multiple

[feanil]

@Colin-Fredericks let me know if you want to work through the rebasing together.

[Colin-Fredericks]

@feanil I ran into some issues changing old commits because of the merge, so the force push was to undo that. Is this better?

[Colin-Fredericks]

Hmm, ok, linting still failing so it's still seeing the old commits.

[Colin-Fredericks]

AHA! Got it to drop the old commits from the pull request.

[feanil]

Nice, thanks Colin, I'll merge and release these changes!