On 28/02/2010 01:22, Antoine Pitrou wrote:
Le Fri, 26 Feb 2010 14:29:03 -0800, Guido van Rossum a écrit :
Byte-code only wasn't always supported. We added it knowing full well it
had all those problems (plus, it locks in the Python version), simply
because a certain class of developers won't stop asking for it. Their
users are apparently too dumb to decode bytecode but smart enough to
read source code, even if they don't understand it, and this knowledge
could hurt them.
The idea that too much knowledge hurts users doesn't sound very Pythonic
to me.

As I understand it, the people interested in bytecode-only distributions
are commercial companies willing to ease support. Why don't they whip up
a specialized importer, and perhaps make it available as a recipe or a
PyPI module somewhere? The idea that we should provide built-in support
for a stupid (non-)security mechanism sounds insane to me.

Finally, the sight of commercial companies not being able to do their
work and begging open source projects to do it for them makes me *yawn*.
If you aren't proficient or motivated enough to build your own internal
commodities, perhaps you shouldn't do claim to do business at all.

Well if we'd *never* had this feature this argument would be very strong indeed. On the other hand if we want them to switch to Python 3 - but by the way we cut one of the features you rely on, but don't worry all you have to do is recode it yourself - doesn't make a very convincing argument.

Michael Foord

regards

Antoine.

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk


--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

READ CAREFULLY. By accepting and reading this email you agree, on behalf of 
your employer, to release me from all obligations and waivers arising from any 
and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, 
clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and 
acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your 
employer, its partners, licensors, agents and assigns, in perpetuity, without 
prejudice to my ongoing rights and privileges. You further represent that you 
have the authority to release me from any BOGUS AGREEMENTS on behalf of your 
employer.


_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to