gaussdb-django 5.2.1: License Compliance, Documentation Improvements & Minor Release #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is a minor release focused on license compliance, documentation accuracy, and usability improvements for the
5.2(Django 5.2-compatible) branch.Key highlights:
LICENSEwith explicit Django attribution noticeNo functional changes to the database backend itself.
Changes Made
LICENSEfilegaussdb_django/(including newly addedexpressions.py)pyproject.toml:5.2.0→5.2.1Framework :: Django :: 5.2example/wagtail_README.md):/opt/django_work/...to user-home~/django_work/...for better portabilityinstall_gaussdb_driver.shfor openEuler/HCE detection5.2.0branchTesting
pipLICENSEfile inclusion on PyPI test instanceAdditional Notes
gaussdb-django==5.2.1.