Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!1.eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <antoon.pardon@rece.vub.ac.be>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.001
X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; '16,': 0.03; 'received:134': 0.05; '"as': 0.07; 'stack.': 0.07; 'debugger': 0.09; 'exception,': 0.09; 'frameworks,': 0.09; 'happens.': 0.09; 'stderr': 0.09; 'exception': 0.13; 'stack': 0.13; 'thu,': 0.15; 'variables': 0.15; 'clear.': 0.16; 'received:ac.be': 0.16; 'stuff,': 0.16; 'sure.': 0.16; 'wrote:': 0.16; '2015': 0.20; 'fine,': 0.22; 'trace': 0.22; 'variables.': 0.22; 'header:In- Reply-To:1': 0.24; 'header:User-Agent:1': 0.26; "doesn't": 0.26; 'chris': 0.26; 'values': 0.28; 'subject:/': 0.30; 'code': 0.30; 'received:be': 0.30; 'generally': 0.32; 'lets': 0.33; 'info': 0.34; 'list': 0.34; 'done': 0.35; 'something': 0.35; 'level': 0.35; 'should': 0.36; 'to:addr:python-list': 0.36; 'pm,': 0.36; 'subject:: ': 0.37; 'stuff': 0.38; 'mean': 0.38; 'whatever': 0.39; 'application': 0.39; 'to:addr:python.org': 0.40; 'some': 0.40; 'more': 0.63; 'grab': 0.64; 'jul': 0.72; 'pardon': 0.84; 'unclear': 0.84; 'drops': 0.91
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak8IADvAp1WGuA9G/2dsb2JhbABahCwkgyTAFQKCGQEBAQEBAYUvAQEEI1URCxgCAgUWCwICCQMCAQIBRRMGAgKIKro1kSaEeAEBCAIggSKKKoUNFoJSgUMBBJRGjBiIO5BEJmODG20BgkoBAQE
Date: Thu, 16 Jul 2015 16:32:52 +0200
From: Antoon Pardon <antoon.pardon@rece.vub.ac.be>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-Version: 1.0
To: python-list@python.org
Subject: Re: Possibly Pythonic Tail Call Optimization (TCO/TRE)
References: <CAD+URuj-4e62-9hvpiLsrBP1M6kXRyZhZ6XyL01gWWnDoShvNg@mail.gmail.com> <CAPTjJmr92j+2DDPsZxynoHyZTTCpc-48cWCVrx_fT3dA0j_Osg@mail.gmail.com> <55A3C366.6060602@rece.vub.ac.be> <mailman.468.1436796350.3674.python-list@python.org> <87fv4r1fre.fsf@jester.gateway.sonic.net> <mailman.481.1436851550.3674.python-list@python.org> <87bnff1eks.fsf@jester.gateway.sonic.net> <mailman.499.1436874241.3674.python-list@python.org> <87d1zunctp.fsf@elektro.pacujo.net> <mailman.503.1436878550.3674.python-list@python.org> <87k2u2eu67.fsf@elektro.pacujo.net> <CAPTjJmqtTRHpNZHByn1pKNSfbsG6X--s2d_G0FopKxDugqpjdA@mail.gmail.com> <55A51662.4090007@rece.vub.ac.be> <mo4a7g$mkg$1@ger.gmane.org> <mailman.531.1436951405.3674.python-list@python.org> <d0o60cF8ubiU1@mid.individual.net> <55A75DE0.1070101@rece.vub.ac.be> <CAPTjJmoWqhZ_P890qug3Zf=VjJOBmO5kOSaX08PDF3FdNyLFNA@mail.gmail.com> <55A7B80B.6090905@rece.vub.ac.be> <CAPTjJmp3mupnenUYYNmvJpNr27zx_CdHQ9m6wkEFi-Lz+Evw9A@mail.gmail.com>
In-Reply-To: <CAPTjJmp3mupnenUYYNmvJpNr27zx_CdHQ9m6wkEFi-Lz+Evw9A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.20+
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.587.1437057181.3674.python-list@python.org>
Lines: 18
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1437057181 news.xs4all.nl 2885 [2001:888:2000:d::a6]:50220
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:93932

On 07/16/2015 04:00 PM, Chris Angelico wrote:
> On Thu, Jul 16, 2015 at 11:56 PM, Antoon Pardon
> <antoon.pardon@rece.vub.ac.be> wrote:
>> Fine, I should have been more clear.
>>
>> The stack trace as it is generally produced on stderr after an uncought
>> exception, doesn't contain the values of the variables on the stack.
> Sure. So you catch it at top level and grab whatever info you need. In
> some frameworks, this is already done for you - an uncaught exception
> from application code drops you into a debugger that lets you explore
> and even execute code at any level in the stack.

What is unclear about "as it is generally produced on stderr"? That you
can do a whole lot of stuff, doesn't mean that this whole lot of stuff is
part of what generally happens. When people on this list ask a person
to include the stacktrace with the description of the problem, they
don't mean something that includes the values of the variables.