Re: [pypy-dev] ZODB3

2012/3/22 Armin Rigo : > On Wed, Mar 21, 2012 at 20:46, Amaury Forgeot d'Arc > wrote: >> Persistent.__getstate__ uses _PyObject_GetDictPtr(), which always >> returns NULL in cpyext. > > Does it make sense?  Shouldn't it be unimplemented, or raise a > warning, or something? The first time I encou

Re: [pypy-dev] ZODB3

Hi, On Wed, Mar 21, 2012 at 20:46, Amaury Forgeot d'Arc wrote: > Persistent.__getstate__ uses _PyObject_GetDictPtr(), which always > returns NULL in cpyext. Does it make sense? Shouldn't it be unimplemented, or raise a warning, or something? A bientôt, Armin.

Re: [pypy-dev] ZODB3

2012/3/21 Armin Rigo : > On Fri, Mar 2, 2012 at 11:03, Aroldo Souza-Leite wrote: >>    data = self.__dict__.pop('_container') >> KeyError: '_container' > > Last I heard, the Persistent base class, written in C, uses old tricks > that are kind of deprecated; if I remember correctly, before Python >

Re: [pypy-dev] ZODB3

Hi, On Fri, Mar 2, 2012 at 11:03, Aroldo Souza-Leite wrote: >    data = self.__dict__.pop('_container') > KeyError: '_container' Last I heard, the Persistent base class, written in C, uses old tricks that are kind of deprecated; if I remember correctly, before Python 2.2, it was known as the pla

Re: [pypy-dev] ZODB3

Hi list, now ZODB3 and zope.testing can be pip-installed in a PyPy virtual environment and the tests can be called. But the tests fail. The same tests pass in CPython2.7. Could somebody please make a short comment on this before I eventually forward the case to the ZODB department? The att

Re: [pypy-dev] ZODB3

Hi, On Tue, Feb 28, 2012 at 10:55, Aroldo Souza-Leite wrote: > Oh, does that mean that this problem could be solved by the PyPy people? Yes. Fixed in b741ab752493. The easiest is to wait for next night's automatic builds, but you can also try it out directly by replacing the file Include/objec

Re: [pypy-dev] ZODB3

Hi, Am 28.02.2012 10:42, schrieb Armin Rigo: Hi, On Tue, Feb 28, 2012 at 10:09, Aroldo Souza-Leite wrote: thanks, I'll try and take the issue to the zodb-...@zope.org. Ah, that's not what I meant. I meant that we can just add a do-nothing _Py_ForgetReference in PyPy and be done. A bientôt

Re: [pypy-dev] ZODB3

Hi, On Tue, Feb 28, 2012 at 10:09, Aroldo Souza-Leite wrote: > thanks, I'll try and take the issue to the zodb-...@zope.org. Ah, that's not what I meant. I meant that we can just add a do-nothing _Py_ForgetReference in PyPy and be done. A bientôt, Armin. _

Re: [pypy-dev] ZODB3

Hi Armin, hi Maciej, hi list, thanks, I'll try and take the issue to the zodb-...@zope.org. Cheers. Aroldo. Am 27.02.2012 16:48, schrieb Armin Rigo: Hi, On Mon, Feb 27, 2012 at 16:29, Maciej Fijalkowski wrote: On PyPy it probably should not do anything so you can maybe try with #define _Py

Re: [pypy-dev] ZODB3

Hi, On Mon, Feb 27, 2012 at 16:29, Maciej Fijalkowski wrote: > On PyPy it probably should not do anything so you can maybe try with > #define _Py_ForgetReference(obj), but I don't actually know. Yes, it looks like it doesn't do anything in release builds of CPython. It's there for debugging.

Re: [pypy-dev] ZODB3

On Mon, Feb 27, 2012 at 1:53 AM, Aroldo Souza-Leite wrote: > Hi list, > > just to keep you informed: > > the ZODB3 can be successfully installed in a PyPy-1.8 virtual environment, > but the tests fail. Below is the whole bash session I tried on Ubuntu LTS. > For the PyPy developers the interesting

[pypy-dev] ZODB3

Hi list, just to keep you informed: the ZODB3 can be successfully installed in a PyPy-1.8 virtual environment, but the tests fail. Below is the whole bash session I tried on Ubuntu LTS. For the PyPy developers the interesting part might be the last section, "Running the ZODB3 tests". Thanks