Re: [Zope-dev] [ZODB-Dev] RFC: release persistent as a standalone package
Hi Tres, I'm +1 on the change even without the answer to my next question, but can you elaborate on what is the advantage of releasing persistent appart from ZODB? Regards, Leo On Sat, Jun 30, 2012 at 8:02 PM, Tres Seaver <tseaver@palladion.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I have completed the work needed to make 'persistent' distributable as a standalone package. The effort (begun almost four years ago!) includes the following highlights:
Platform Changes - ----------------
- - Added explicit support for Python 3.2 and PyPy.
- Note that the C implementations of Persistent, PickleCache, and Timestamp are not built (yet) on these platforms.
- - Dropped explicit support for Python < 2.6.
- - Completed pure-Python reference implementations of 'Persistent', 'PickleCache', and 'TimeStamp'.
Testing Changes - ---------------
- - 100% unit test coverage.
- - All covered platforms tested under 'tox'.
- - Refactored some doctests as unittests.
- - Removed all 'ZODB'-dependent tests:
- Rewrote some to avoid the dependency
- Cloned the remainder into new 'ZODB.tests' modules on the ZODB trunk.
- - Added support for continuous integration using 'tox' and 'jenkins'.
- - Added 'setup.py dev' alias (installs 'nose' and 'coverage').
- - Dropped dependency on 'zope.testing' / 'zope.testrunner': tests now run with 'setup.py test'.
Documentation Changes - ---------------------
- - Refactored many doctests as Sphinx documentation (snippets are exercised via 'tox').
- - Added 'setup.py docs' alias (installs 'Sphinx' and 'repoze.sphinx.autointerface').
I would like to release a '4.0.0' version of the package, and switch the ZODB trunk to pull it in as a dependency (deleting the currently included (older) copy of persistent). One possible issue is that I have not (yet) made the C extensions work under Python 3.2: I don't know whether that should be a blocker for a release.
Comments?
Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/vPyMACgkQ+gerLs4ltQ4DsgCfRsKhBzvTWHehVI86I5sryhjF whQAoL3evyI6GKOfa7eDVjTUVh7B8Q+/ =82vd -----END PGP SIGNATURE-----
_______________________________________________ For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
On 1 July 2012 02:16, Leonardo Rochael Almeida <leorochael@gmail.com> wrote:
I'm +1 on the change even without the answer to my next question, but can you elaborate on what is the advantage of releasing persistent appart from ZODB?
As well as the clearer separation of concerns it opens up the possibility for other persistence systems to adopt persistent for detecting changes to mapped objects, gaining the benefit of its fast C implementation. The BTrees package is also useful outside the context of the ZODB. Laurence
participants (2)
-
Laurence Rowe -
Leonardo Rochael Almeida