Is your feature request related to a problem? Please describe.
I am currently upgrading my project's dependency tree to support Django 6.0 (which was officially released in April). However, upgrading is blocked because django-flatpickr specifies a strict upper-bound version constraint in its package metadata (Django >=2,<6), causing dependency resolution failures during installation.
Describe the solution you'd like
I would like the package configuration (pyproject.toml) to be updated to bump the allowed upper bound to officially support Django 6.x.
Describe alternatives you've considered
I have actively tested the current version of django-flatpickr locally in a Django 6.0 environment, and all the custom widgets, assets, and options continue to function perfectly under the hood without any issues. The only blocker is the strict PyPI installation metadata.
Additional context
Thank you for maintaining this package!
Is your feature request related to a problem? Please describe.
I am currently upgrading my project's dependency tree to support Django 6.0 (which was officially released in April). However, upgrading is blocked because
django-flatpickrspecifies a strict upper-bound version constraint in its package metadata (Django >=2,<6), causing dependency resolution failures during installation.Describe the solution you'd like
I would like the package configuration (
pyproject.toml) to be updated to bump the allowed upper bound to officially support Django 6.x.Describe alternatives you've considered
I have actively tested the current version of
django-flatpickrlocally in a Django 6.0 environment, and all the custom widgets, assets, and options continue to function perfectly under the hood without any issues. The only blocker is the strict PyPI installation metadata.Additional context
Thank you for maintaining this package!