> On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka wrote:
>
> On 28.11.16 09:06, Benjamin Peterson wrote:
>> I've have just updated PEP 373 to say that Python 2.7.13 release
>> candidate 1 will be released on December 3. The final will follow two
>> weeks later on December 17. If there are delays
On 11/28/2016 10:42 AM, Guido van Rossum wrote:
Perhaps (un)related, is the release schedule for 3.5.3 set yet? (I'm
holding off putting a new version of typing.py on typeshed until
that's out.)
Not set in stone, but I have a rough plan. I want the dust to settle
around 3.6 first. So, have
Perhaps (un)related, is the release schedule for 3.5.3 set yet? (I'm
holding off putting a new version of typing.py on typeshed until that's
out.)
On Mon, Nov 28, 2016 at 10:36 AM, Serhiy Storchaka
wrote:
> On 28.11.16 09:06, Benjamin Peterson wrote:
>
>> I've have just updated PEP 373 to say th
On 28.11.16 09:06, Benjamin Peterson wrote:
I've have just updated PEP 373 to say that Python 2.7.13 release
candidate 1 will be released on December 3. The final will follow two
weeks later on December 17. If there are delays in the process, the
final will likely to pushed into January.
Could
Hi Christian and thanks for the fast reply,
It's great to hear that the latest version is working fine. Do you have anymore
details on the fix/breakage?
The latest commit at Fedora's rawhide openssl package is at [0]. Is it missing
something?
[0]
http://pkgs.fedoraproject.org/cgit/rpms/opens
On 2016-11-28 16:35, Charalampos Stratakis wrote:
> Hello,
>
> Escalating here an issue that seems that it should be tagged as blocker.
>
> Currently the latest version of openssl-1.1.0c breaks Python's test suite.
>
> The problematic commit was identified [0] and reverted [1] at openssl's
> up
Hello,
Escalating here an issue that seems that it should be tagged as blocker.
Currently the latest version of openssl-1.1.0c breaks Python's test suite.
The problematic commit was identified [0] and reverted [1] at openssl's
upstream, however when running the test suite on a Fedora Rawhide ma
Ok, thanks. I pushed my patch.
Victor
2016-11-27 16:37 GMT+01:00 Jeremy Hylton :
> I don't think there's any need to keep this feature. I hope we have better
> ways to profile function and method calls now than we did when this code was
> submitted.
>
> Jeremy
>
>
> On Sat, Nov 26, 2016 at 3:34 A
