Re: [Python-Dev] Does anyone use CALL_PROFILE special build?
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 AM Raymond Hettinger > wrote: >> >> >> > On Nov 25, 2016, at 1:28 AM, Victor Stinner >> > wrote: >> > >> > I would like to completely remove the feature to be able to implement >> > further optimizations. >> >> This seems reasonable to me. I've never used or needed this special >> build; StackOverflow has no mention of it; and a Google search comes up >> nearly empty. That said, it might be worthwhile to check with Jeremy to >> get his thoughts before removing his code. >> >> >> Raymond ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Tests breakage with latest openssl (issue28689)
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 machine, which includes the fix, the tests currently hang (not just failing like before). The issue, with some more details, is tracked here: https://bugs.python.org/issue28689 [0] https://github.com/openssl/openssl/issues/1903 [1] https://github.com/openssl/openssl/commit/beacb0f0c1ae7b0542fe053b95307f515b578eb7 Regards, Charalampos Stratakis Associate Software Engineer Python Maintenance Team, Red Hat ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tests breakage with latest openssl (issue28689)
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 > upstream, however when running the test suite on a Fedora Rawhide machine, > which includes the fix, the tests currently hang (not just failing like > before). > > The issue, with some more details, is tracked here: > https://bugs.python.org/issue28689 > > [0] https://github.com/openssl/openssl/issues/1903 > [1] > https://github.com/openssl/openssl/commit/beacb0f0c1ae7b0542fe053b95307f515b578eb7 Hi Charalampos, Python's 3.6 and default (3.7) tests suite is passing with OpenSSL 1.1.0d-dev (OpenSSL_1_1_0-stable branch). Maybe your backport is missing a fix? Christian ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Tests breakage with latest openssl (issue28689)
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/openssl.git/commit/?id=e443a79334446ac0dc14fdf7c062386f92bbc7a0 Regards, Charalampos Stratakis Associate Software Engineer Python Maintenance Team, Red Hat - Original Message - From: "Christian Heimes" To: python-dev@python.org Sent: Monday, November 28, 2016 6:03:34 PM Subject: Re: [Python-Dev] Tests breakage with latest openssl (issue28689) 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 > upstream, however when running the test suite on a Fedora Rawhide machine, > which includes the fix, the tests currently hang (not just failing like > before). > > The issue, with some more details, is tracked here: > https://bugs.python.org/issue28689 > > [0] https://github.com/openssl/openssl/issues/1903 > [1] > https://github.com/openssl/openssl/commit/beacb0f0c1ae7b0542fe053b95307f515b578eb7 Hi Charalampos, Python's 3.6 and default (3.7) tests suite is passing with OpenSSL 1.1.0d-dev (OpenSSL_1_1_0-stable branch). Maybe your backport is missing a fix? Christian ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/cstratak%40redhat.com ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python 2.7.13 release dates
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 it be delayed until 3.6.0 released? I paused fixing non-critical and non-documentation bugs while 3.6 in pre-release stage and this could include bugs that affect 2.7. In additional, we always receive increased number of bug reports in the first one or two weeks after releasing new Python version. Some of these reports are about regressions introduced by bugfixes. If delay bugfix releases after new version release, we could fix regressions caused by backported bugfixes and make bugfix releases more reliable. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python 2.7.13 release dates
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 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 it be delayed until 3.6.0 released? I paused fixing non-critical and > non-documentation bugs while 3.6 in pre-release stage and this could > include bugs that affect 2.7. > > In additional, we always receive increased number of bug reports in the > first one or two weeks after releasing new Python version. Some of these > reports are about regressions introduced by bugfixes. If delay bugfix > releases after new version release, we could fix regressions caused by > backported bugfixes and make bugfix releases more reliable. > > > > ___ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido% > 40python.org > -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python 2.7.13 release dates
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 an RC1 in January, and then the final release two weeks later. I'm traveling the second week of January (#DSDad) so the RC would be either before or after that. //arry/ ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python 2.7.13 release dates
> 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 in the process, the >> final will likely to pushed into January. > > Could it be delayed until 3.6.0 released? I paused fixing non-critical and > non-documentation bugs while 3.6 in pre-release stage and this could include > bugs that affect 2.7. > > In additional, we always receive increased number of bug reports in the first > one or two weeks after releasing new Python version. Some of these reports > are about regressions introduced by bugfixes. If delay bugfix releases after > new version release, we could fix regressions caused by backported bugfixes > and make bugfix releases more reliable. +1 on delaying 2.7.13 for a bit. As long as it doesn't muck up Benjamin's schedule, the extra time would be helpful (Python 3.6.0 got all the focus recently). Raymond ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
