RetroSearch Browse

Fri Mar 6 23:47:08 CET 2015 · https://mail.python.org/pipermail/python-dev/2015-March/138641.html

On Sat, 7 Mar 2015 09:34:20 +1100
Steven D'Aprano <steve at pearwood.info> wrote:

> On Fri, Mar 06, 2015 at 09:37:05PM +0100, Antoine Pitrou wrote:
> > On Fri, 06 Mar 2015 18:11:19 +0000
> > Brett Cannon <brett at python.org> wrote:
> > > And the dropping of docstrings does have an impact on
> > > memory usage when you use Python at scale.
> > 
> > What kind of "scale" are you talking about? Do you have any numbers
> > about such impact?
> > 
> > > You're also assuming that we will never develop an AST optimizer
> > 
> > No, the assumption is that we don't have such an optimizer *right now*.
> > Having command-line options because they might be useful some day is
> > silly.
> 
> Quoting the PEP:
> 
>     This issue is only compounded when people optimize Python 
>     code beyond what the interpreter natively supports, e.g., 
>     using the astoptimizer project [2]_.

The astoptimizer project is not part of Python. It's third-party
software that has no relationship to .pyo files.

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-March/138641.html below:

[Python-Dev] PEP 488: elimination of PYO files