Re: [Python-Dev] Accessing value stack

2013-01-07 Thread Maciej Fijalkowski
On Mon, Jan 7, 2013 at 10:40 PM, PJ Eby wrote: > On Mon, Jan 7, 2013 at 11:32 AM, Brett Cannon wrote: >> On Mon, Jan 7, 2013 at 10:46 AM, Maciej Fijalkowski wrote: >>> On Mon, Jan 7, 2013 at 4:22 PM, Oleg Broytman wrote: On Mon, Jan 07, 2013 at 03:06:51PM +0100, Dima Tisnek wrote: >

Re: [Python-Dev] Accessing value stack

2013-01-07 Thread PJ Eby
On Mon, Jan 7, 2013 at 11:32 AM, Brett Cannon wrote: > On Mon, Jan 7, 2013 at 10:46 AM, Maciej Fijalkowski wrote: >> On Mon, Jan 7, 2013 at 4:22 PM, Oleg Broytman wrote: >>> On Mon, Jan 07, 2013 at 03:06:51PM +0100, Dima Tisnek >>> wrote: Hi, is it possible to access the values stored on

Re: [Python-Dev] Accessing value stack

2013-01-07 Thread Brett Cannon
On Mon, Jan 7, 2013 at 10:46 AM, Maciej Fijalkowski wrote: > On Mon, Jan 7, 2013 at 4:22 PM, Oleg Broytman wrote: >> Hello. >> >>We are sorry but we cannot help you. This mailing list is to work on >> developing Python (adding new features to Python itself and fixing bugs); >> if you're havin

Re: [Python-Dev] Accessing value stack

2013-01-07 Thread Maciej Fijalkowski
On Mon, Jan 7, 2013 at 4:22 PM, Oleg Broytman wrote: > Hello. > >We are sorry but we cannot help you. This mailing list is to work on > developing Python (adding new features to Python itself and fixing bugs); > if you're having problems learning, understanding or using Python, please > find a

Re: [Python-Dev] Accessing value stack

2013-01-07 Thread Oleg Broytman
Hello. We are sorry but we cannot help you. This mailing list is to work on developing Python (adding new features to Python itself and fixing bugs); if you're having problems learning, understanding or using Python, please find another forum. Probably python-list/comp.lang.python mailing list/

[Python-Dev] Accessing value stack

2013-01-07 Thread Dima Tisnek
Hi, is it possible to access the values stored on the stack in Python stack machine from Python? As in, consider expression: tmp = foo() + bar() At the point in time when bar() is called, foo() already returned something, and that value is on top of the stack in that frame, a few steps after bar