Skip to main content

Zope-like transaction manager via WSGI middleware

Project description

repoze.tm2 (Transaction Manager)

Middleware which uses the ZODB transaction manager to wrap a call to its pipeline children inside a transaction. This is a fork of the repoze.tm package which depends only on the transaction package rather than the entirety of ZODB (for users who don’t rely on ZODB).

See docs/index.rst for documentation.

1.0a5 (2009/9/7)

  • Don’t commit after aborting if the transaction was doomed or if the commit veto aborted.

  • Don’t use “real” transaction module in tests.

  • 100% test coverage.

1.0a4 (2009/1/6)

  • RESTify CHANGES, move docs in README.txt into Sphinx.

  • Remove setup.cfg (all dependencies available via PyPI).

  • Synchronization point with repoze.tm (0.9).

1.0a3

Allow commit_veto hook to be specified within Paste config, ala:

[filter:tm]
use = repoze.tm:make_tm
commit_veto = some.package:myfunction

myfunction should take three args: environ, status, headers and should return True if the txn should be aborted, False if it should be committed.

Initial PyPI release.

1.0a2 (2008/7/15)

1.0a1

  • Fork point: we’ve created repoze.tm2, which is repoze.tm that has a dependency only on the ‘transaction’ package instead of all of ZODB.

  • Better documentation for non-Zope usage in README.txt.

0.8

  • Relaxed requirement for ZODB 3.7.2, since we might need to use the package with other verions. Note that the tests which depend on transaction having “doom” semantics don’t work with 3.7.2, anyway.

0.7

  • Depend on PyPI release of ZODB 3.7.2. Upgrade to this by doing bin/easy_install -U ‘ZODB3 >= 3.7.1, < 3.8.0a’ if necessary.

0.6

  • after_end.register and after_end.unregister must now be passed a transaction object rather than a WSGI environment to avoid the possibility that the WSGI environment used by a child participating in transaction management won’t be the same one used by the repoze.tm package.

  • repoze.tm now inserts a key into the WSGI environment (repoze.tm.active) if it’s active in the WSGI pipeline. An API function, repoze.tm:isActive can be called with a single argument, the WSGI environment, to check if the middleware is active.

0.5

  • Depend on rerolled ZODB 3.7.1 instead of zopelib.

  • Add license and copyright, change trove classifiers.

0.4

  • Depend on zopelib rather than ZODB 3.8.0b3 distribution, because the ZODB distribution pulls in various packages (zope.interface and ZEO most notably) that are incompatible with stock Zope 2.10.4 apps and older sandboxes. We’ll need to revisit this.

0.3

  • Provide limited compatibility for older transaction package versions which don’t support the ‘transaction.isDoomed’ API.

0.2

  • Provide after_end API for registering callbacks at transaction end.

0.1

  • Initial Release

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

repoze.tm2-1.0a5.tar.gz (19.4 kB view details)

Uploaded Source

File details

Details for the file repoze.tm2-1.0a5.tar.gz.

File metadata

  • Download URL: repoze.tm2-1.0a5.tar.gz
  • Upload date:
  • Size: 19.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No

File hashes

Hashes for repoze.tm2-1.0a5.tar.gz
Algorithm Hash digest
SHA256 1af458d74934e0486c01de8f21be941f7937e8e8d0ff07062eb65eca48e709b9
MD5 e874e84259b753dd0157260412d61173
BLAKE2b-256 4420a1963c8ee4771fef67b32e9fc07dd25a6ddcfc5d7d8bfc0b6d193ea6f7eb

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page