devel/py-django-rq 4.2.0

devel/py-django-rq: update to 1.2.0

Reported by:	portscout

Use PY_FLAVOR for dependencies.

FLAVOR is the current port's flavor, it should not be used outside of
this scope.

Sponsored by:	Absolight

www/py-django-annotations: switch to django 1.11

PR:		228229
Submitted by:	Kai <freebsd_ports@k-worx.org>
Approved by:	rene (devel/py-django-rq maintainer)

devel/py-django-rq: update to version 1.1.0

- make 'make test' work
- update MASTER_SITES and WWW to point to new repository

Reported by:	portscout
Changelog:	https://github.com/rq/django-rq/blob/master/CHANGELOG.md

Fix RUN_DEPENDS

Reported by:	pkg-fallout

devel/py-django-rq: force dependency on Django 1.8 for now to prevent breaking www/py-django-annotations

Reported by:	antoine

Use the Django meta-port for my Django port to avoid conflicts between them.

Bump PORTREVISIONs

devel/py-django-rq: update to version 1.0.1

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
  current python flavor.  It can be used in dependency lines when the
  port itself is not python flavored.  For example, deskutils/calibre.

  By default, all the flavors are generated.  To only generate flavors
  for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
  BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.

  In all the ports with Python dependencies, the *_DEPENDS entries MUST
  end with the flavor so that the framework knows which to build/use.
  This is done by appending '@${PY_FLAVOR}' after the origin (or
  @${FLAVOR} if in a Python module with Python flavors, as the content
  will be the same).  For example:

    RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}

PR:		223071
Reviewed by:	portmgr, python
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D12464

devel/py-django-rq: update to v1.0.0

Submitted by:	portscout

devel/py-django-rq: update to 0.9.6

- Django 1.10 and scalability fixes
- Pet portlint by moving USES up

devel/py-django-rq: update to 0.9.5

Submitted by:	portscout

devel/py-django-rq: update to 0.9.4

Reported by:	portscout

devel/py-django-rq: update to 0.9.3

Submitted by:	portscout

www/py-django-rq: use TEST_TARGET instead of manual commands

Submitted by:	mat

devel/py-django-rq: update to 0.9.2, add test target

Submitted by:	portscout

devel/py-django-rq: update to 0.9.1

Submitted by:	portscout

Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.

With hat:	portmgr
Sponsored by:	Absolight

- Switch forgotten ports over to py-django18 - Fix PYTHON_PKGNAMEPREFIX

Reported by:    antoinebot

devel/py-django-rq: update to version 0.9.0

Update minimal versions for dependencies.
Submitted by:	portscout

- Update MAINTAINER: use @FreeBSD.org

Django integration with RQ, a Redis based Python queuing library. Django-RQ is a simple app that allows you to configure your queues in django's settings.py and easily use them in your project.

WWW: https://github.com/ui/django-rq/