On Friday, May 10, 2013 11:01:33 PM Tres Seaver wrote:
> > Tres, are we ready to commit to a zope.security 4.0.0 as well?
>
> AFAIK, we could cut it from the 'master' at any time. I don't know of
> any issues I don't see any open launchpad issues which should block a
> release.
Cool, we can do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/10/2013 07:55 PM, Stephan Richter wrote:
> On Friday, May 10, 2013 05:04:31 PM Tres Seaver wrote:
>> I pushed out a ZODB 4.0.0b1 release after the merge. If the
>> buildbots stay green over the weekend, I think we can release a
>> 4.0.0 final ea
On Friday, May 10, 2013 05:04:31 PM Tres Seaver wrote:
> I pushed out a ZODB 4.0.0b1 release after the merge. If the buildbots
> stay green over the weekend, I think we can release a 4.0.0 final early
> next week.
Awesome thanks. After the 4.0.0 final release, I will set aside some time for
the
On Fri, May 10, 2013 at 5:04 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/08/2013 12:34 PM, Tres Seaver wrote:
>> On 04/29/2013 08:37 PM, Stephan Richter wrote:
>>> Well, that's the py3 branch. As Tres mentioned, zodbpickle is ready
>>> for Py3 with noload() s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/08/2013 12:34 PM, Tres Seaver wrote:
> On 04/29/2013 08:37 PM, Stephan Richter wrote:
>> Well, that's the py3 branch. As Tres mentioned, zodbpickle is ready
>> for Py3 with noload() support. I totally agree that we do not need
>> to solve any of
On Wednesday, May 08, 2013 12:34:00 PM Tres Seaver wrote:
> > I do not care whether this happens for ZODB 4.0 or 4.1 as long as I
> > get some commitment that 4.1
>
> Chris and I chatted with Jim about this over beers last Friday. I
> explained that the current 'py3; branch does not require the '
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/29/2013 08:37 PM, Stephan Richter wrote:
> Well, that's the py3 branch. As Tres mentioned, zodbpickle is ready
> for Py3 with noload() support. I totally agree that we do not need to
> solve any of the transition work now.
>
> So for ZODB Py3 su
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
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).
Regards,
Stephan
--
Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/28/2013 07:19 PM, Jim Fulton wrote:
> I'm confused. I don't understand why we need a Python 3 pickler
> change to support the new Python 2 binary type. I thought we were
> going to pickle Python 2 binary objects using the standard Python 3
>
On Fri, Apr 26, 2013 at 8:02 PM, Stephan Richter
wrote:
> On Friday, April 26, 2013 05:34:15 PM Tres Seaver wrote:
>> I would like to merge this branch to master early next week and make a
>> release, so that we can evaluate merging the 'py3' branch of ZODB.
>>
>> Thoughts? Note that I have not y
On Wed, Apr 17, 2013 at 2:54 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/16/2013 05:13 PM, Stephan Richter wrote:
>> On Tuesday, April 16, 2013 04:38:06 PM Tres Seaver wrote:
>>> Comments?
>
> (I don't now why Stephan's e-mail didn't make it to the list).
>
>
On Tue, Apr 16, 2013 at 4:38 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> After getting a bit bogged down during the PyCon US 2013 sprints, I'd
> like to restart the discussion by outlining the problem as I think I
> understand it now.
>
> Proposal for ZODB pickle c
On Friday, April 26, 2013 05:34:15 PM Tres Seaver wrote:
> I would like to merge this branch to master early next week and make a
> release, so that we can evaluate merging the 'py3' branch of ZODB.
>
> Thoughts? Note that I have not yet addressed the portions of my proposal
> which deal with ana
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/16/2013 04:38 PM, Tres Seaver wrote:
> - ``zodbpickle`` should provide a new ``binary`` type which Python2
> applications can begin using to signal that attributes should be
> unpickled in Py3k as ``bytes``. See:
> https://github.com/zopefou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/16/2013 05:19 PM, Stephan Richter wrote:
> Oh, I see that in your branch of ``zodbpickle`` you already added
> protocol 3 support to the Py2.7 cPickle code. Does this code also run
> under Py3.3?
(I don't now why Stephan's e-mail didn't make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/16/2013 05:13 PM, Stephan Richter wrote:
> On Tuesday, April 16, 2013 04:38:06 PM Tres Seaver wrote:
>> Comments?
(I don't now why Stephan's e-mail didn't make it to the list).
> The big omission that I noticed while reading the text carefully
On Tue, Apr 16, 2013 at 5:38 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> [...]
>
> Concrete Proposal
> - -
>
> I believe we will need to update ``zodbpickle`` and ``ZDOB`` to allow
> for any of the strategies to be applied.
>
> - - ``zodbpickle`` sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After getting a bit bogged down during the PyCon US 2013 sprints, I'd
like to restart the discussion by outlining the problem as I think I
understand it now.
Proposal for ZODB pickle compatibility
==
Issues
- -
31 matches
Mail list logo
