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/2010-April/099475.html below:

[Python-Dev] PEP 3147 ready for pronouncement and merging

[Python-Dev] PEP 3147 ready for pronouncement and merging [Python-Dev] PEP 3147 ready for pronouncement and mergingGuido van Rossum guido at python.org
Sat Apr 17 04:44:55 CEST 2010
Thanks for all the changes!

On Fri, Apr 16, 2010 at 4:00 PM, Barry Warsaw <barry at python.org> wrote:
> On Apr 15, 2010, at 08:01 PM, Guido van Rossum wrote:
>>Hm. I wish there was a way to find out whether the bytecode (or
>>whatever) actually *was* read from this file. __file__ in Python 2
>>supports this (though not in Python 3).
>
> Do you have a use case for that?  It might be interesting to know, but I can't
> think of a good way to infer that from __file__ and __cached__, or of a good
> way to expose that on module objects.   Of course, it would be totally Python
> implementation dependent too.

The only use case I can think of is a unit test that would indirectly
assess that bytecode was (or wasn't) read in specific conditions. You
can safely ignore this use case.

-- 
--Guido van Rossum (python.org/~guido)
More information about the Python-Dev mailing list

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