A slick app that supports automatic or manual queryset caching and automatic
granular event-driven invalidation.
It uses redis as backend for ORM cache and redis or filesystem for simple
time-invalidated one.
And there is more to it:
* Decorators to cache any user function or view as a queryset or by time
* Extensions for django and jinja2 templates
* Transparent transaction support
* Dog-pile prevention mechanism
* A couple of hacks to make django faster
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 py311-django-cacheops listed in the above command, you can pick from the names under the Packages section.
*: 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
python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal
Any missed ports, feel free to bump.
Any ports that need setuptools at runtime can have the devel/py-setuptools
manually added back to RUN_DEPENDS, but understand that this practice
is deprecated; see CHANGES for details.
*: Switch consumers over to Django 4.2
Django 3.2 reached its End-of-Life on 1st April 2024 and Django 4.2 is
the new LTS (= Long Term Support) release which will be supported until
April 2026.
* Switch most ports that use www/py-django32 to www/py-django42.
* Ports that are not compatible with Django 3.2 have already been set
with an expiration date were not taken into account.
* Bump PORTREVISION due dependency change where necessary.
PR: 276319
Reviewed by: dvl, grembo, ultima
Approved by: bofh (implicit), dvl, grembo, Kevin Golding, sunpoet,
ultima, maintainer timeout (remaining maintainers)
Differential Revision: https://reviews.freebsd.org/D44637
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
www/py-django-cacheops: Update to 6.1
* Simplify the CONFLICTS_INSTALL entry as well. This also reduces
editing of the Makefile if another port need to be "repo-copied"
(e.g. for Django 4.1) based on this port in the future.
Changelog:
https://github.com/Suor/django-cacheops/blob/6.1/CHANGELOG
www/py-django32: Switch consumers over to Django 3.2
Django 2.2 became End-of-Life on 11th April 2022 and Django 3.2 is the
new LTS (= Long Term Support) release which will be supported until
April 2024.
* Switch the most ports that use www/py-django22 to www/py-django32
* Switch www/seahub over to www/py-djangorestframework
* Ports that are not yet ready for Django 3.2 (only three so far) or
those that have already been set with an expiration date were not
taken into account.
* Bump PORTREVISION due dependency change where necessary.
PR: 261313
Reviewed by: bofh, dvl, koobs, ultima
Approved by: bofh, dvl, koobs, ultima, sunpoet, Kevin Golding, Ivan Rozhuk,
Alexander Sieg (maintainers)
maintainer timeout (remaining maintainers)
Differential Revision: https://reviews.freebsd.org/D34859
*: Create Django 3.2 ports for net-mgmt/netbox
* Django 2.2 is currently the "default" version in the ports tree due
its long term support until April 2022. Thus ports that are assigned
to that version will exist until then.
The following ports are required to make the upgrade of
net-mgmt/netbox to the 2.11 release possible because it requires
Django 3.2. All of the ports listed below were created on the basis
of their respective original ports:
- devel/py-dj32-django-rq
- www/py-dj32-django-auth-ldap
- www/py-dj32-django-cacheops (updated to a newer release)
- www/py-dj32-django-cors-headers
(Only the first 15 lines of the commit message are shown above )
Create some ports that are assigned to Django 3.1 instead Django 2.2
* Django 2.2 is currently the "default" version in the ports tree due its
long term support until April 2022. Thus ports that are assigned to that
version will exist until then.
The following ports are required to make the upgrade of net-mgmt/netbox to
the 2.9 release possible because it requires Django 3.1 and provides no
backwards compatibility for previous versions of Django.
- www/py-dj31-django-rq
(copied from r539662 to use the 2.3.2 release for now)
- www/py-dj31-django-auth-ldap
- www/py-dj31-django-cacheops
- www/py-dj31-django-cors-headers
(Only the first 15 lines of the commit message are shown above )
Assign some ports I maintain from Django 1.11 to Django 2.2
Django 1.11 is End-of-Life since April 2020 thus switch the following ports
to Django 2.2 (which has LTS support until April 2022):
* www/py-django-auth-ldap
* www/py-django-cacheops
* www/py-django-filter
* www/py-django-prometheus
Adjust the required Python version as Django 2.2 needs at least Python 3.5+
and bump the PORTREVISION for package change.
Mark the related py-dj22-* port variants as DEPRECATED because they're
obsolete now. Don't set an expiration date yet as they're still used by
some consumers and a few more Django 1.11 ports need to be assigned to
Django 2.2 first.
New port: www/py-dj22-django-cacheops
Repocopy www/py-django-cacheops and assign it to Django 2.2. That port will
be required for the upcoming update of net-mgmt/netbox to 2.6.
Also limit the port to Python 3.5+ as Django 2.2 requires it as minimum
dependency and add the related CONFLICTS_INSTALL entries.
New port: www/py-django-cacheops
A slick app that supports automatic or manual queryset caching and automatic
granular event-driven invalidation.
It uses redis as backend for ORM cache and redis or filesystem for simple
time-invalidated one.
And there is more to it:
* Decorators to cache any user function or view as a queryset or by time
* Extensions for django and jinja2 templates
* Transparent transaction support
* Dog-pile prevention mechanism
* A couple of hacks to make django faster
WWW: https://github.com/Suor/django-cacheops
Approved by: mentors (implicit)
