Armin Rigo wrote:
> Yuk! Not renamed to .py files. Distributing .py files that are
> actually bytecode looks like a new funny way to create confusion. No, I
> was half-heartedly musing about introducing Yet Another file extension
> (.pyc for caching and .pyX for importable bytecode, or possibly
Hi Steven,
On Wed, Nov 22, 2006 at 11:48:44PM -0700, Steven Bethard wrote:
> (... pyc files ...)
> For people wanting to ship just bytecode, the cached
> .pyc files could be renamed to .py files and then those could be
> shipped and imported.
Yuk! Not renamed to .py files. Distributing .py file
Here's the summary for the first half of November. Try not to spend it
all in one place! ;-)
As always, corrections and comments are greatly appreciated.
=
Announcements
=
--
Python 2.5 malloc families
--
Just a reminder t
