Re: [Python-Dev] Obtaining stack-frames from co-routine objects

2015-06-01 Thread Yury Selivanov
Hi Ben, On 2015-05-31 8:35 AM, Ben Leslie wrote: Hi Yury, I'm just starting my exploration into using async/await; all my 'real-world' scenarios are currently hypothetical. One such hypothetical scenario however is that if I have a server process running, with some set of concurrent connection

Re: [Python-Dev] cpython (2.7): Issue #24357: Change host in socket.getaddrinfo example to one that

2015-06-01 Thread Ned Deily
On Jun 1, 2015, at 20:46, Serhiy Storchaka wrote: > On 02.06.15 04:58, ned.deily wrote: >> https://hg.python.org/cpython/rev/30da21d2fa4f >> changeset: 96458:30da21d2fa4f >> branch: 2.7 >> parent: 96454:5e8fa1b13516 >> user:Ned Deily >> date:Mon Jun 01 18:45:49 2015 -0

Re: [Python-Dev] RM for 3.6?

2015-06-01 Thread Serhiy Storchaka
On 01.06.15 21:07, Barry Warsaw wrote: On May 30, 2015, at 10:09 AM, Serhiy Storchaka wrote: Isn't it a time to assign release manager for 3.6-3.7? Indeed! Please welcome Ned Deily as RM for 3.6: https://www.python.org/dev/peps/pep-0494/ Good news for all us! Ned many times saved me from

Re: [Python-Dev] cpython (2.7): Issue #24357: Change host in socket.getaddrinfo example to one that

2015-06-01 Thread Serhiy Storchaka
On 02.06.15 04:58, ned.deily wrote: https://hg.python.org/cpython/rev/30da21d2fa4f changeset: 96458:30da21d2fa4f branch: 2.7 parent: 96454:5e8fa1b13516 user:Ned Deily date:Mon Jun 01 18:45:49 2015 -0700 summary: Issue #24357: Change host in socket.getaddrinfo examp

Re: [Python-Dev] RM for 3.6?

2015-06-01 Thread Mark Lawrence
On 01/06/2015 19:33, Benjamin Peterson wrote: On Mon, Jun 1, 2015, at 14:24, Stefan Behnel wrote: Barry Warsaw schrieb am 01.06.2015 um 20:07: On May 30, 2015, at 10:09 AM, Serhiy Storchaka wrote: Isn't it a time to assign release manager for 3.6-3.7? Indeed! Please welcome Ned Deily as R

Re: [Python-Dev] [python-committers] Ned Deily is release manager for Python 3.6

2015-06-01 Thread Larry Hastings
On 06/01/2015 11:09 AM, Barry Warsaw wrote: Please welcome Ned Deily as RM for Python 3.6. https://www.python.org/dev/peps/pep-0494/ We're in good hands. For two versions now Benjamin and Ned have been quietly cleaning up my mistakes after (nearly) every release. My guess is, Ned won't both

Re: [Python-Dev] Python 3 migration status update across some key subcommunities (was Re: 2.7 is here until 2020, please don't call it a waste.)

2015-06-01 Thread Ludovic Gasc
2015-05-31 16:15 GMT+02:00 Nick Coghlan : > On 31 May 2015 at 19:07, Ludovic Gasc wrote: > > About Python 3 migration, I think that one of our best control stick is > > newcomers, and by extension, Python trainers/teachers. > > If newcomers learn first Python 3, when they will start to work > > p

Re: [Python-Dev] RM for 3.6?

2015-06-01 Thread Chris Angelico
On Tue, Jun 2, 2015 at 5:05 AM, Skip Montanaro wrote: > > > On Mon, Jun 1, 2015 at 1:35 PM, Ned Deily wrote: >> >> I thought I was volunteering to get a pony. I was misinformed. > > > Ned, > > Not to worry. I'm sure that by the time 3.6a0 is due, the PSF will be able to > scrape together the fu

Re: [Python-Dev] Windows new 3.5 installer: Command line uninstall

2015-06-01 Thread Paul Moore
On 1 June 2015 at 20:21, Steve Dower wrote: > You need the original exe and can pass /uninstall to that. OK, that's cool. Looks like I missed that in the docs. (Checks) Yes, I did :-( Paul ___ Python-Dev mailing list Python-Dev@python.org https://mail.

Re: [Python-Dev] Windows new 3.5 installer: Command line uninstall

2015-06-01 Thread Steve Dower
You need the original exe and can pass /uninstall to that. There is an uninstall entry in the registry that uses the cached version of the exe (via Programs and Features), but I don't know why WMI doesn't see it. I'll check that out a bit later. You can uninstall with the web installer exe, and

Re: [Python-Dev] RM for 3.6?

2015-06-01 Thread Skip Montanaro
On Mon, Jun 1, 2015 at 1:35 PM, Ned Deily wrote: > I thought I was volunteering to get a pony. I was misinformed. Ned, Not to worry. I'm sure that by the time 3.6a0 is due, the PSF will be able to scrape together the funds for a pony, perhaps even one with super powers: Skip __

Re: [Python-Dev] RM for 3.6?

2015-06-01 Thread Ned Deily
> On Jun 1, 2015, at 11:33, Benjamin Peterson wrote: > > > > On Mon, Jun 1, 2015, at 14:24, Stefan Behnel wrote: >> Barry Warsaw schrieb am 01.06.2015 um 20:07: >>> On May 30, 2015, at 10:09 AM, Serhiy Storchaka wrote: Isn't it a time to assign release manager for 3.6-3.7? >>> >>> Indeed!

Re: [Python-Dev] RM for 3.6?

2015-06-01 Thread Benjamin Peterson
On Mon, Jun 1, 2015, at 14:24, Stefan Behnel wrote: > Barry Warsaw schrieb am 01.06.2015 um 20:07: > > On May 30, 2015, at 10:09 AM, Serhiy Storchaka wrote: > >> Isn't it a time to assign release manager for 3.6-3.7? > > > > Indeed! Please welcome Ned Deily as RM for 3.6: > > > > https://www.p

Re: [Python-Dev] [Python-checkins] peps: We have a 3.6 release PEP.

2015-06-01 Thread Ned Deily
> On Jun 1, 2015, at 11:04, Yury Selivanov wrote: > > It looks like we now have two 3.6 release PEPs: 494 & 495 Sorry about the confusion. The second checkin (for 495) has been reverted; PEP 494 will be the ongoing PEP. ___ Python-Dev mailing list

Re: [Python-Dev] RM for 3.6?

2015-06-01 Thread Stefan Behnel
Barry Warsaw schrieb am 01.06.2015 um 20:07: > On May 30, 2015, at 10:09 AM, Serhiy Storchaka wrote: >> Isn't it a time to assign release manager for 3.6-3.7? > > Indeed! Please welcome Ned Deily as RM for 3.6: > > https://www.python.org/dev/peps/pep-0494/ Does he know already? Stefan __

Re: [Python-Dev] RM for 3.6?

2015-06-01 Thread Barry Warsaw
On May 30, 2015, at 10:09 AM, Serhiy Storchaka wrote: >Isn't it a time to assign release manager for 3.6-3.7? Indeed! Please welcome Ned Deily as RM for 3.6: https://www.python.org/dev/peps/pep-0494/ Cheers, -Barry pgpArSFCqg7XM.pgp Description: OpenPGP digital signature

Re: [Python-Dev] [Python-checkins] peps: We have a 3.6 release PEP.

2015-06-01 Thread Yury Selivanov
It looks like we now have two 3.6 release PEPs: 494 & 495 Yury On 2015-06-01 1:59 PM, barry.warsaw wrote: https://hg.python.org/peps/rev/a50d51e8c748 changeset: 5888:a50d51e8c748 user:Barry Warsaw date:Mon Jun 01 13:59:32 2015 -0400 summary: We have a 3.6 release PEP. fil

Re: [Python-Dev] Avoiding reference leaks in heap types with custom tp_dealloc

2015-06-01 Thread Antoine Pitrou
On Mon, 01 Jun 2015 12:09:37 -0400 Benjamin Peterson wrote: > > I thought all the slots were supposed to be available through the stable > ABI, since you need them to properly define c types. You're right, I was thinking specifically about the ABI versioning issues (which I exposed in my reply t

Re: [Python-Dev] Avoiding reference leaks in heap types with custom tp_dealloc

2015-06-01 Thread Benjamin Peterson
On Mon, Jun 1, 2015, at 11:33, Antoine Pitrou wrote: > On Mon, 1 Jun 2015 16:38:35 +0200 > Petr Viktorin wrote: > > Hello, > > The new test_importlib.extension.test_loader is currently leaking > > references, (issue24268). There is a simple hack to stop this, but I'm > > inclined to not apply qu

Re: [Python-Dev] Avoiding reference leaks in heap types with custom tp_dealloc

2015-06-01 Thread Antoine Pitrou
On Mon, 1 Jun 2015 17:52:13 +0200 Petr Viktorin wrote: > On Mon, Jun 1, 2015 at 5:33 PM, Antoine Pitrou wrote: > > On Mon, 1 Jun 2015 16:38:35 +0200 > > Petr Viktorin wrote: > [...] > >> The nice way out would be taking advantage of PEP 442: xxlimited.Xxo > >> can ditch tp_dealloc in favor of tp

Re: [Python-Dev] Avoiding reference leaks in heap types with custom tp_dealloc

2015-06-01 Thread Petr Viktorin
On Mon, Jun 1, 2015 at 5:33 PM, Antoine Pitrou wrote: > On Mon, 1 Jun 2015 16:38:35 +0200 > Petr Viktorin wrote: [...] >> The nice way out would be taking advantage of PEP 442: xxlimited.Xxo >> can ditch tp_dealloc in favor of tp_traverse and tp_finalize (the >> former of which it needs anyway to

Re: [Python-Dev] Avoiding reference leaks in heap types with custom tp_dealloc

2015-06-01 Thread Antoine Pitrou
On Mon, 1 Jun 2015 16:38:35 +0200 Petr Viktorin wrote: > Hello, > The new test_importlib.extension.test_loader is currently leaking > references, (issue24268). There is a simple hack to stop this, but I'm > inclined to not apply quick hacks and rather dig into the root cause. > (It's a test module

[Python-Dev] Avoiding reference leaks in heap types with custom tp_dealloc

2015-06-01 Thread Petr Viktorin
Hello, The new test_importlib.extension.test_loader is currently leaking references, (issue24268). There is a simple hack to stop this, but I'm inclined to not apply quick hacks and rather dig into the root cause. (It's a test module, the refleaks are relatively harmless.) The tests are based dire

[Python-Dev] Windows new 3.5 installer: Command line uninstall

2015-06-01 Thread Paul Moore
I'm trying to script a command line uninstall of Python 3.5. The new installer has a nice well-documented command line interface, but there's nothing much about how to uninstall. Looking at the installed products, I see >get-wmiobject Win32_Product -filter 'name like "Python 3.5.0b2%"' | select N

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-06-01 Thread Paul Sokolovsky
Hello, On Mon, 01 Jun 2015 13:14:27 +0200 "M.-A. Lemburg" wrote: [] > > The "7.0x faster" number on speed.pypy.org would be significantly > > *higher* if we upgraded the baseline to 2.7.10 now. > > If someone were to volunteer to set up and run speed.python.org, > I think we could add some add

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-06-01 Thread M.-A. Lemburg
On 01.06.2015 12:44, Armin Rigo wrote: > Hi Larry, > > On 31 May 2015 at 01:20, Larry Hastings wrote: >> p.s. Supporting this patch also helps cut into PyPy's reported performance >> lead--that is, if they ever upgrade speed.pypy.org from comparing against >> Python *2.7.2*. > > Right, we should

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

2015-06-01 Thread Armin Rigo
Hi Larry, On 31 May 2015 at 01:20, Larry Hastings wrote: > p.s. Supporting this patch also helps cut into PyPy's reported performance > lead--that is, if they ever upgrade speed.pypy.org from comparing against > Python *2.7.2*. Right, we should do this upgrade when 2.7.11 is out. There is some

Re: [Python-Dev] [RELEASED] Python 3.5.0b2 is now available

2015-06-01 Thread Nick Coghlan
Thanks Larry, and my apologies to the release team for the extra work! Regards, Nick. ___ 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/a