[Python-Dev] cpython (3.3): don't run frame if it has no stack (closes #17669) (original) (raw)
Maciej Fijalkowski fijall at gmail.com
Thu Apr 11 12:38:06 CEST 2013
- Previous message: [Python-Dev] cpython (3.3): don't run frame if it has no stack (closes #17669)
- Next message: [Python-Dev] cpython (3.3): don't run frame if it has no stack (closes #17669)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Apr 11, 2013 at 12:28 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
On 11 Apr 2013 07:49, "Antoine Pitrou" <solipsis at pitrou.net> wrote:
On Wed, 10 Apr 2013 23:01:46 +0200 (CEST) benjamin.peterson <python-checkins at python.org> wrote: > http://hg.python.org/cpython/rev/35cb75b9d653 > changeset: 83238:35cb75b9d653 > branch: 3.3 > parent: 83235:172f825d7fc9 > user: Benjamin Peterson <benjamin at python.org> > date: Wed Apr 10 17:00:56 2013 -0400 > summary: > don't run frame if it has no stack (closes #17669) Wouldn't it be better with a test? Benjamin said much the same thing on the issue, but persuading the interpreter to create a frame without a stack that then gets exposed to this code path isn't straightforward :P Cheers, Nick.
Maybe it's worth understanding in which circumstances this holds? Please write a test, we'll run into similar issue at some point Im'm sure.
Cheers, fijal
- Previous message: [Python-Dev] cpython (3.3): don't run frame if it has no stack (closes #17669)
- Next message: [Python-Dev] cpython (3.3): don't run frame if it has no stack (closes #17669)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]