A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-May/004294.html below:

[Python-Dev] py_compile and CR in source files

[Python-Dev] py_compile and CR in source files [Python-Dev] py_compile and CR in source filesGreg Ward gward@mems-exchange.org
Fri, 26 May 2000 11:06:09 -0400
On 26 May 2000, Skip Montanaro said:
> I don't think you can safely compile modules by importing them.  You have no
> idea what the side effects of the import might be.

Yeah, that's my concern.

> How about fixing py_compile.compile() instead?

Would be a good thing to do this for Python 1.6, but I can't go back and
fix all the Python 1.5.2 installations out there.

Does anyone know if any good reasons why 'import' and
'py_compile.compile()' are different?  Or is it something easily
fixable?

        Greg



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