When dealing with internationalization in JavaScript code, Django provides
the javascript_catalog view which sends out a JavaScript code library with
functions that mimic the gettext interface, plus an array of translation
strings.
At first glance, it works well and everything is fine. But, because
javascript_catalog view is generating JavaScript catalog dynamically
on each request, it's adding an overhead that can be an issue with site
growth.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py312-django_statici18n listed in the above command, you can pick from the names under the Packages section.
www/py-django_statici18n: Update to 2.7.1
* Assume maintainership.
* Switch to the PEP517 build framework to make the port future-proof.
* Use the more preferred DISTVERSION and fix LICENSE as well.
Changelog since 2.6.0:
https://github.com/zyegfryed/django-statici18n/blob/v2.7.1/docs/changelog.rst
PR: 297808
Reported by: Christos Longros
Co-authored-by: Kai Knoblich <kai@FreeBSD.org>
*: Switch consumers over to Django 5.2
Django 4.2 reached its End-of-Life on 7th April 2026 and Django 5.2 is
the new LTS (= Long Term Support) release which will be supported until
April 2028.
* Switch most ports that use www/py-django42 to www/py-django52.
* Where necessary, remove PORTSCOUT, which is no longer needed because
an update to a newer version that no longer supports Django 4.2 should
now be possible.
* Bump PORTREVISION due dependency change where necessary.
PR: 291707
Reviewed by: sunpoet (python)
Differential Revision: https://reviews.freebsd.org/D56966
net-mgmt/seafile-server,www/seahub: Deprecate
Updating www/seahub, and especially net-mgmt/seafile-server, is more
difficult than originally anticipated. The current version of www/seahub
also only runs with Django 4.2, which has been end-of-life since April.
Before www/seahub and net-mgmt/seafile-server are marked as BROKEN after
the migration of the affected ports to Django 5.2 [1], and then vanish
from the ports tree at the end of 2026Q2 - which would also break POLA
due the short time period - do the following to buy some time for a
possible update:
* Create required py-dj42-* ports and switch www/seahub to them. These
py-dj42-* ports were copied from their original counterparts, are
bound to Django 4.2, and have also been adapted for the PEP517 build
(Only the first 15 lines of the commit message are shown above )
