Re: [Python-Dev] cpython (merge 3.4 -> default): null merge with 3.4

2015-06-14 Thread Ned Deily
In article <20150615003717.2599.82...@psf.io>, senthil.kumaran wrote: > https://hg.python.org/cpython/rev/9a0c5ffe7420 > changeset: 96605:9a0c5ffe7420 > parent: 96603:47a566d6ee2a > parent: 96604:3ded282f9615 > user:Senthil Kumaran > date:Sun Jun 14 17:37:09 2015 -070

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

2015-06-14 Thread Mark Lawrence
On 14/06/2015 11:50, Ben Leslie wrote: Per Nick's advice I've created enhancement proposal 245340 with an attached patch. http://bugs.python.org/issue24450 as opposed to http://bugs.python.org/issue24450#msg245340 :) -- My fellow Pythonistas, ask not what our language can do for you, ask wh

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

2015-06-14 Thread Nick Coghlan
On 14 Jun 2015 19:17, "Guido van Rossum" wrote: > > A good plan. I think this could be added to 3.5 still? It's a pretty minor adjustment to the PEP 492 machinery, really. Good point - as per Ben's original post, the lack of it makes it quite hard to get a clear picture of the system state when u

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

2015-06-14 Thread Ben Leslie
Per Nick's advice I've created enhancement proposal 245340 with an attached patch. On 14 June 2015 at 19:16, Guido van Rossum wrote: > A good plan. I think this could be added to 3.5 still? It's a pretty minor > adjustment to the PEP 492 machinery, really. > > On Sat, Jun 13, 2015 at 6:16 PM, Nic

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

2015-06-14 Thread Guido van Rossum
A good plan. I think this could be added to 3.5 still? It's a pretty minor adjustment to the PEP 492 machinery, really. On Sat, Jun 13, 2015 at 6:16 PM, Nick Coghlan wrote: > > On 14 Jun 2015 10:01, "Ben Leslie" wrote: > > > > If this seems like a good approach I'll try and work it in to a > >