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

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

[Python-Dev] disable writing .py[co]

• Previous message: [Python-Dev] disable writing .py[co]
• Next message: [Python-Dev] disable writing .py[co]
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Guido van Rossum <guido@python.org> writes:
> 
> > What's the problem with compiling mm_cfg.py or site.py?  As long as
> > you don't delete the .py file, the .pyc file acts only as a cache.  I
> > see no need to avoid compilation.
> 
> If you change the configuration file, Python will try to regenerate
> the .pyc file. This is a problem for people who don't want pyc files
> written at program execution time.

Ok, but weren't we going to give those people an explicit option?

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

• Previous message: [Python-Dev] disable writing .py[co]
• Next message: [Python-Dev] disable writing .py[co]
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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