Skip to content

feat: Add Django 6.0 support#3

Open
joseanoxp wants to merge 1 commit into
Azure-Samples:mainfrom
joseanoxp:feature/django-6.0-support
Open

feat: Add Django 6.0 support#3
joseanoxp wants to merge 1 commit into
Azure-Samples:mainfrom
joseanoxp:feature/django-6.0-support

Conversation

@joseanoxp
Copy link
Copy Markdown

Summary

This PR adds support for Django 6.0 by updating the version constraint.

Changes

  • Updated Django version constraint from >=3.2,<6 to >=3.2,<7
  • Added Python 3.13 to classifiers
  • Updated comment with Django 6.0 documentation link

Rationale

Django 6.0 was released in December 2024. After reviewing the codebase, particularly identity/django.py, I found that this library only uses stable Django APIs:

  • django.shortcuts.redirect
  • django.shortcuts.render
  • django.urls.include
  • django.urls.path
  • django.urls.reverse

None of these APIs have breaking changes in Django 6.0. The library should work without any code modifications.

Testing

Tested with a Django 6.0 project and confirmed the library works correctly with the updated constraint.

References

- Update Django version constraint from `<6` to `<7`
- Add Python 3.13 to classifiers
- Update comment with Django 6.0 documentation link

Django 6.0 uses only stable APIs (django.shortcuts, django.urls) that
have not changed. Tested with Django 6.0 release.
@joseanoxp
Copy link
Copy Markdown
Author

FYI: I opened a parallel PR in the upstream maintained by Ray Luo — rayluo/identity#64 — applying the same constraint widening (django>=3.2,<7) and Python 3.13 classifier.

That repo is what publishes the identity package to PyPI (this Azure-Samples copy is installed via git+ per the docs), so a merge there is what reaches pip install identity[django] users. The new PR also closes rayluo/identity#62 (the Django >6 support request).

Cross-referencing both PRs for visibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant