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-March/098104.html below:

[Python-Dev] Breaking bytecode only imports (was Re: __file__)

[Python-Dev] Breaking bytecode only imports (was Re: __file__)Guido van Rossum guido at python.org
Wed Mar 3 00:27:05 CET 2010
On Tue, Mar 2, 2010 at 11:52 AM, Barry Warsaw <barry at python.org> wrote:
> On Mar 02, 2010, at 09:34 AM, Guido van Rossum wrote:
>
>>On Tue, Mar 2, 2010 at 5:03 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>>> P.S. I actually started this thread as a +0 to the idea of dropping
>>> bytecode only imports. Over the course of the discussion I've shifted to
>>> a firm -1 in the absence of some proper comparative benchmarks to
>>> justify the change in semantics.
>>
>>FWIW, I started at -1 and am still -1. I think the PEP is overreaching
>>in this aspect; it does not serve the stated purpose of the PEP to
>>make life easier for distros that share code between Python versions.
>
> I think that's fair, and just the guidance I'm looking for.  By now you
> understand the pros and cons, so if this is a pronouncement, I will cement it
> into the PEP.

Yes, and thanks!

-- 
--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