On approximately 3/3/2010 5:49 PM, came the following characters from
the keyboard of Barry Warsaw:
On Mar 03, 2010, at 07:37 PM, Jim Jewett wrote:
>I understand the need to ship without source -- but why does that
>require supporting .pyc (or .pyo) -only?
>
>Couldn't vendors just replace the real .py files with empty files?
Yes, I think that's a possibility. What would people think about that?
-Barry
That's kooky, but not as kooky as my idea. As mentioned elsewhere,
timestamps would have to be treated carefully.
In this scenario, the .pyc files would still live in __pycache__ ?
Complete with the foo.<token>.pyc naming ?
So one could actually create a "fat .zip" application that could work
with a variety of installed Python versions ??? Hmm...
--
Glenn -- http://nevcal.com/
===========================
A protocol is complete when there is nothing left to remove.
-- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking
_______________________________________________
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
