Re: Backward compatibility (was Re: Announcing Newt DB, the amphibious database)
Jim Fulton <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Message-ID | <CAPDm-Fj2QGHzSy5gfz0pZjtZZ29h04g7xpp2=7dtOJ+XB90uWA@mail.gmail.com> |
On Fri, Feb 24, 2017 at 5:50 AM, Hanno Schlichting <[email protected]> wrote: > On Fri, Feb 24, 2017, at 05:47, Jim Fulton wrote: > > Thank you for trying. > > Can you point me at something I can check out to beat on this myself? > > > If you really want to, > I really want current Plone to be able to use use current ZODB (and Newt :)), so yes, I really want to. > you could try to fix up tempstorage [1]. That one only depends on the ZODB > and includes a fairly standard buildout / tox setup. > > So something like this should work: > > $ git clone [email protected]:zopefoundation/tempstorage.git > $ cd tempstorage > $ python2.7 bootstrap.py > $ bin/buildout > $ bin/test > > On master, testing against ZODB 5 / transaction 2 that currently has 13 > errors for me. > > You can also run bin/tox to test against multiple Python versions. There's > also a travis-ci setup to do that same testing, which gets triggered for > the usual new branches or pull requests. > > Since tempstorage was already a separate project in Zope 2.13, someone > should be able to use a new release of it together with ZODB 5 / > transaction 2 in current Plone versions. > Thanks. Jim -- Jim Fulton http://jimfulton.info -- You received this message because you are subscribed to the Google Groups "zodb" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.