Retarget 2.1.0 deprecation to django-pgware - #33
Merged
Merged
Conversation
The 2.1.0 final/shim release pointed at django-pg-utils, but the actual successor on PyPI is django-pgware 1.0.0. Correct the dependency, the DeprecationWarning, the README, and the CHANGELOG to point at django-pgware, and surface the deprecation in the PyPI-visible Summary field. The import path (django_pg_utils.locks) is unchanged: django-pgware installs under that distribution name but ships the django_pg_utils module.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
The
django-pglocks2.1.0 final/shim release pointed at django-pg-utils, but the actual successor published on PyPI is django-pgware 1.0.0. This corrects every distribution-name reference.Changes
django-pg-utils>=0.1.0→django-pgware>=1.0.0;Summarynow leads withDEPRECATED — consolidated into django-pgwareso the deprecation is visible in PyPI search results and the page header.DeprecationWarningtext retargeted to django-pgware.Notes
django-pglocksis 1.0.4; the committed 2.0.0/2.1.0 were never uploaded, so 2.1.0 is corrected in place.from django_pg_utils.locks import …— django-pgware installs under that distribution name but ships thedjango_pg_utilsmodule, so the import resolves once it's installed.Development Status :: 7 - Inactiveclassifier was already present.Verified
uv buildproduces a clean 2.1.0 wheel withSummary: DEPRECATED…,Requires-Dist: django-pgware>=1.0.0, andClassifier: Development Status :: 7 - Inactive.