Created attachment 233716 [details]
attached is a patch that would deprecate www/py-django-modern-rpc and set an expiration date to it as the current version of the port doesn't seem to work with Django 3.2.
There's also 1.0.0 Alpha available at the upstream repository, which contain support for Django 3.2, that might be used.
Another option would be, if the 0.12.1 release (not available at PyPI) of www/py-django-modern-rpc still works with Django 3.2, to switch the port over to Django 3.2.
Which of these options would you prefer?
I'm OK to deprecate this port. Thanks!
Comment on attachment 233716 [details]
^Triage: Setting maintainer-approval flag to '+' as it was given via comment #1.
A commit in branch main references this bug:
Author: Kai Knoblich <kai@FreeBSD.org>
AuthorDate: 2022-05-14 04:45:18 +0000
Commit: Kai Knoblich <kai@FreeBSD.org>
CommitDate: 2022-05-14 04:45:18 +0000
www/py-django-modern-rpc: Deprecate/Set to expire
* Django 2.2 is End-of-Life since April 2022 and the current release of
this port isn't compatible with newer versions of Django.
Approved by: sunpoet (maintainer)
www/py-django-modern-rpc/Makefile | 3 +++
1 file changed, 3 insertions(+)
(In reply to Po-Chuan Hsieh from comment #1)