On Monday, April 29, 2013 01:15:29 PM Tres Seaver wrote:
> FWIW, we have reports that some brave souls have successfully built Py3k
> apps using the 'py3' branch.
Yep, see here:
https://github.com/CipherHealth/cipher.uibuilderdemo
This is not an app in production, but shows off some features of
On Monday, April 29, 2013 01:50:22 PM Jim Fulton wrote:
> Whether 4.0 supports Python 3 or not, let's quickly get to the point where
> tests are run and pass on both Python 2 and 3. Once we get to that point,
> we won't accept pull requests that break Python 3 (or 2, of course).
> But let's get to
On Mon, Apr 29, 2013 at 1:15 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/29/2013 12:44 PM, Jim Fulton wrote:
>> Yes. There are lots of features I'd like to add to ZODB. I tend to
>> work on them when I have time (infrequently) or where we have a
>> driving
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/29/2013 12:44 PM, Jim Fulton wrote:
> Yes. There are lots of features I'd like to add to ZODB. I tend to
> work on them when I have time (infrequently) or where we have a
> driving need at ZC. Long ZODB release cycles provide a lot of stop
> e
On Mon, Apr 29, 2013 at 12:25 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/29/2013 11:00 AM, Jim Fulton wrote:
>> Let's keep master stable. Maybe someone will want to add features
>> before the Python 3 support is stable. I don't want to hold 4.1
>> hostage e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/29/2013 11:00 AM, Jim Fulton wrote:
> Let's keep master stable. Maybe someone will want to add features
> before the Python 3 support is stable. I don't want to hold 4.1
> hostage either.
Given that the only folks (besides maybe you) invested i
On Mon, Apr 29, 2013 at 10:54 AM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/29/2013 10:51 AM, Jim Fulton wrote:
>
>> Right. As I suggested, let's get to a point where we can get a stable
>> ZODB 4.0 release for Python 2. As soon as we get that, let's get a
>>
On Mon, Apr 29, 2013 at 10:20 AM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/29/2013 09:48 AM, Jim Fulton wrote:
>> On Sun, Apr 28, 2013 at 8:34 PM, Stephan Richter
>> wrote:
>>> On Sunday, April 28, 2013 07:23:12 PM Jim Fulton wrote:
Can ZODB 4 be used no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/29/2013 10:51 AM, Jim Fulton wrote:
> Right. As I suggested, let's get to a point where we can get a stable
> ZODB 4.0 release for Python 2. As soon as we get that, let's get a
> ZODB 4.0.x or 4.1 release that works on Python 3, presumably via
On Mon, Apr 29, 2013 at 10:24 AM, Stephan Richter
wrote:
> On Monday, April 29, 2013 09:48:05 AM Jim Fulton wrote:
>> I'd like there to a stable 4.0 release **soon**
>> that doesn't use zodbpickle for Python 2.
>
> I would like to agree. But on the other hand, the ZODB release cycles are very
> lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/29/2013 09:48 AM, Jim Fulton wrote:
> On Sun, Apr 28, 2013 at 8:34 PM, Stephan Richter
> wrote:
>> On Sunday, April 28, 2013 07:23:12 PM Jim Fulton wrote:
>>> Can ZODB 4 be used now without zodbpickle?
>>
>> No, unfortunately for Py2 we need t
On Monday, April 29, 2013 09:48:05 AM Jim Fulton wrote:
> I'd like there to a stable 4.0 release **soon**
> that doesn't use zodbpickle for Python 2.
I would like to agree. But on the other hand, the ZODB release cycles are very
long and the prospect of waiting another 6-12 months before any Pyth
On Sun, Apr 28, 2013 at 8:34 PM, Stephan Richter
wrote:
> On Sunday, April 28, 2013 07:23:12 PM Jim Fulton wrote:
>> Can ZODB 4 be used now without zodbpickle?
>
> No, unfortunately for Py2 we need the custom cPickle and for Py3 `noload()`
> support (as Tres mentioned).
This is a problem.
The on
13 matches
Mail list logo
