-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/08/2013 02:18 PM, Stephan Richter wrote:
> On Thursday, February 14, 2013 03:42:06 PM Tres Seaver wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 02/14/2013 03:15 PM, Tres Seaver wrote:
>>> The work to create a compatible pure-P
On Thursday, February 14, 2013 03:42:06 PM Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/14/2013 03:15 PM, Tres Seaver wrote:
> > The work to create a compatible pure-Python proxy is partly done (I
> > added tests for all the features of the C version I could disco
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/2013 03:15 PM, Tres Seaver wrote:
> The work to create a compatible pure-Python proxy is partly done (I
> added tests for all the features of the C version I could discover).
> The version I have in my sandbox doesn't pass all those tests, so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/2013 05:02 PM, Tres Seaver wrote:
> On 02/13/2013 11:04 AM, Tres Seaver wrote:
>> On 02/12/2013 10:47 PM, Stephan Richter wrote:
>
>>> I saw you finished test coverage tonight for zope.security. What
>>> is your timeline to do the port to Pyt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/2013 11:04 AM, Tres Seaver wrote:
> On 02/12/2013 10:47 PM, Stephan Richter wrote:
>
>> I saw you finished test coverage tonight for zope.security. What is
>> your timeline to do the port to Python 3? Our efforts are blocked
>> until we get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/12/2013 10:47 PM, Stephan Richter wrote:
> I saw you finished test coverage tonight for zope.security. What is
> your timeline to do the port to Python 3? Our efforts are blocked
> until we get zope.security going. We would be willing to take a
