These tests should validate that any opaque key implementation is a valid opaque key by testing things like the inverse property of serialization and that serialization doesn't change equality.

• Create a new version
• Update Travis to automatically release new tags to PyPI (this may require renaming the package to edx-opaque-keys to avoid confusion)

I am seeing a strange issue with CourseKey.from_string. When I pass u'edX/DemoX/Demo_Course' as an argument in tests, no error is raised. When I pass the same argument while processing a Django request and InvalidKeyError is raised. This issue is present after commit d45d0bd.

It looks like opaque-keys lists pymongo as a dependency in setup.py but I don't see it referenced in the code base. Is this dependency still necessary? Just curious, thanks!

If I did the work to submit a PR to provide for Python 2 and 3 support, would it be accepted?

This repository is a depedency of edx-platform and needs to be upgraded to Python 3.11 before
the Readwood release is cut (mid-April).

• Requirements are compiled with Python 3.8
• Tests are run on Python 3.8 and 3.11
• (Optional) Tests are also run with 3.12 and passing or 3.12 issues are ticketed.
• Classifiers in setup.py setup.cfg or pyproject.toml indicate Python 3.11 support
• A new version is release to PyPI
• A PR is merged to edx-platform to use the new version

The pymongo dependency is pinned to an old version in base.in. Update the pin, update the output .txt files and fix any tests that break.

Newer versions may have breaking changes that may break upstream edx-platform so we should make sure to upgrade opaque keys and pymongo in edx-platform and fix any issues we encounter there as well as a part of this ticket.