A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2003-January/032067.html below:

[Python-Dev] Parallel pyc construction

[Python-Dev] Parallel pyc construction [Python-Dev] Parallel pyc constructionGuido van Rossum guido@python.org
Fri, 10 Jan 2003 13:30:57 -0500
> I hadn't considered the option of not making .pyc files, though I've
> complained about .pyo files in the past with distutils, but now
> compilation is optional there. The .pyc and .pyo files certainly
> clutter a directory. If there is no significant performance
> improvement for loading and using .pyc files or the difference is
> only significant for large files or certain code constructs, maybe
> they shouldn't be automatically created. I guess this is another
> area for test cases.

Oh, in most cases .pyc/.pyo files *do* give significant speedup; the
parser + bytecode compiler are really slow.  It's just that Paul's
machine is so fast and his program runs so long that he doesn't care.
But many people do.

--Guido van Rossum (home page: http://www.python.org/~guido/)



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4