| Port details |
- py-django-transaction-hooks Django database backends to register transaction-commit hooks
- 0.2_3 databases
 =0      0.2_3Version of this port present on the latest quarterly branch.  DEPRECATED: Unmaintained upstream and merged into Django since 1.9
 This port expired on: 2020-07-02
- Maintainer: python@FreeBSD.org
- Port Added: 2015-12-08 20:21:21
- Last Update: 2020-07-02 10:27:00
- SVN Revision: 541031
- Also Listed In: python
- License: BSD3CLAUSE
- WWW:
- https://github.com/carljm/django-transaction-hooks
- Description:
- A better alternative to the native transaction signals of Django.
Sometimes you need to fire off an action related to the current database
transaction, but only if the transaction successfully commits. Examples:
a Celery task, an email notification, or a cache invalidation.
Doing this correctly while accounting for savepoints that might be
individually rolled back, closed/dropped connections, and idiosyncrasies of
various databases, is non-trivial. Transaction signals just make it easier
to do it wrong.
django-transaction-hooks does the heavy lifting so you don't have to.
WWW: https://github.com/carljm/django-transaction-hooks
 cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}django-transaction-hooks>0:databases/py-django-transaction-hooks@${PY_FLAVOR}
- No installation instructions:
- This port has been deleted.
- PKGNAME: py37-django-transaction-hooks
- Package flavors (<flavor>: <package>)
- py37: py37-django-transaction-hooks
- py27: py27-django-transaction-hooks
- distinfo:
- SHA256 (django-transaction-hooks-0.2.tar.gz) = 51bab09547fab673a24d6c59f1df560183b3a49f24a7a5bf35e7eb34ef939e79
SIZE (django-transaction-hooks-0.2.tar.gz) = 7527
No package information for this port in our database- Sometimes this happens. Not all ports have packages.
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py37-setuptools>0 : devel/py-setuptools@py37
- python3.7 : lang/python37
- Runtime dependencies:
-
- py37-django111>=1.11 : www/py-django111@py37
- py37-setuptools>0 : devel/py-setuptools@py37
- python3.7 : lang/python37
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- N/A
- USES:
- python
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
0.2_3
02 Jul 2020 10:27:00
  |
rene |
Remove expired port:
2020-07-02 databases/py-django-transaction-hooks: Unmaintained upstream and
merged into Django since 1.9 |
0.2_3
02 Apr 2020 00:05:48
|
wen |
- Mark DEPRECATED |
0.2_3
08 Mar 2019 14:45:50
|
antoine |
Remove dependency on the django metaport
With hat: portmgr |
0.2_2
14 Oct 2018 15:38:33
|
rene |
Hand over databases/py-django-transaction-hooks to the Python team. |
0.2_2
20 Jun 2018 17:05:44
|
mat |
Use PY_FLAVOR for dependencies.
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight |
0.2_2
06 Mar 2018 22:45:36
|
rene |
Use the Django meta-port for my Django port to avoid conflicts between them.
Bump PORTREVISIONs |
0.2_1
30 Nov 2017 15:50:34
 |
mat |
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  ) |
0.2_1
25 Jun 2017 15:03:55
|
sunpoet |
Fix WWW
Approved by: portmgr (blanket) |
0.2_1
01 Apr 2016 14:00:57
|
mat |
Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.
With hat: portmgr
Sponsored by: Absolight |
0.2_1
16 Jan 2016 11:19:09
|
miwi |
- Switch forgotten ports over to py-django18
- Fix PYTHON_PKGNAMEPREFIX
Reported by: antoinebot |
0.2
25 Dec 2015 07:04:07
|
sunpoet |
- Update MAINTAINER: use @FreeBSD.org |
0.2
08 Dec 2015 20:21:14
|
rene |
A better alternative to the native transaction signals of Django.
Sometimes you need to fire off an action related to the current database
transaction, but only if the transaction successfully commits. Examples:
a Celery task, an email notification, or a cache invalidation.
Doing this correctly while accounting for savepoints that might be
individually rolled back, closed/dropped connections, and idiosyncrasies of
various databases, is non-trivial. Transaction signals just make it easier
to do it wrong.
django-transaction-hooks does the heavy lifting so you don't have to.
WWW: https://github.com/arljm/django-transaction-hooks/ |
As an Amazon Associate I earn from qualifying purchases.