[Python-ideas] Python-ideas Digest, Vol 90, Issue 30

[M.-A. Lemburg]

On 22.05.2014 17:32, Ned Batchelder wrote:
> 
> The whole point of this proposal is to recognize that there are times (debugging, coverage
> measurement) when optimizations are harmful, and to avoid them.

+1

It's regular practice in other languages to disable optimizations
when debugging code. I don't see why Python should be different in this
respect.

Debuggers, testing, coverage and other such tools should be able to
invoke a Python runtime mode that let's the compiler work strictly
by the book, without applying any kind of optimization.

This used to be the default in Python, but over the years, we
gradually moved away from this as default, with no options to get
the old non-optimizing behavior back.

I think it's fine to make safe optimizations default in Python,
but there's definitely a need for being able to run Python in
a debugger without having it perfectly valid skip code lines
(even if they are no ops).

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, May 22 2014)
>>> Python Projects, Consulting and Support ...   http://www.egenix.com/
>>> mxODBC.Zope/Plone.Database.Adapter ...       http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::::: Try our mxODBC.Connect Python Database Interface for free ! ::::::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/