Django is a high-level Python Web framework that encourages rapid development
and clean, pragmatic design.
Developed and used over the past two years by a fast-moving online-news
operation, Django was designed from scratch to handle two challenges: the
intensive deadlines of a newsroom and the stringent requirements of experienced
Web developers. It has convenient niceties for developing content-management
systems, but it's an excellent tool for building any Web site.
WWW: https://www.djangoproject.com/
===> The following configuration options are available for py37-django111-1.11.29_1:
DOCS=on: Build and/or install documentation
HTMLDOCS=off: Install HTML documentation (requires Sphinx)
====> Options available for the group DATABASE
PGSQL=off: PostgreSQL database support
SQLITE=on: SQLite database support
===> Use 'make config' to modify these settings
port moved to www/py-django22 on 2021-04-30 REASON: Has expired: Django 1.11 is End-of-Life since April 2020. Switch to Django 2.2+ as soon as possible
Remove expired ports:
2021-04-30 www/py-django111: Django 1.11 is End-of-Life since April 2020. Switch
to Django 2.2+ as soon as possible.
2021-04-30 archivers/par2cmdline-tbb: Unmaintained upstream, does not build with
oneTbb. Use archivers/par2cmdline instead
www/py-django111: Set to expire
* The port was already marked as DEPRECATED a year ago and all of its
consumers have now been switched to Django 2.2 or newer versions.
PR: 245309
Approved by: kai (python, maintainer)
Update Sphinx
- Repocopy textproc/py-sphinx to textproc/py-sphinx18
Update it to 1.8.5 (latest version from 1.8.X).
This version supports Python 2 and 3.
Add test target.
- textproc/py-sphinx: Update to 3.0.2
Python 3 only (3.5+).
Add test target.
- Mk/Uses/python.mk: Add PY_SPHINX
(Only the first 15 lines of the commit message are shown above )
www/py-django111: Mark as DEPRECATED
Django 1.11 has reached its End-of-Life so mark it as DEPRECATED. Don't set
an EXPIRATION_DATE yet as various consumers need to be switched to
Django 2.2 beforehand, which will happen in the next weeks/months.
When everything is complete there should be no py-dj22-* ports left and the
Ports tree has a few Python 2.7 packages less because Django 2.2 only
supports Python 3.5 or later.
Adjust the description of Django 1.11 of the www/py-django meta-port
accordingly. Also fix a small typo in the Django 2.2 description while I'm
here.
PR: 245309
Reviewed by: koobs, wen (via private e-mail)
Differential Revision: https://reviews.freebsd.org/D24221
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
(Only the first 15 lines of the commit message are shown above )
www/py-django: Add missing runtime dependency
pytz is now a required dependency for Django 1.11 and is strongly
recommended in older releases.
Django 1.11:
https://github.com/django/django/commit/414ad25b090a63eaaf297b1164c8f7d814a710a2
Older releases: docs/topics/i18n/timezones.txt
"3. Should I install pytz?
Yes. Django has a policy of not requiring external dependencies, and for
this reason pytz_ is optional. However, it's much safer to install it."
Reviewed by: lwhsu
MFH: 2017Q3
Differential Revision: https://reviews.freebsd.org/D11835
