Moshe Zadka <[EMAIL PROTECTED]> writes:
> Only CPython uses .pycs. Stackless uses the same PYCs as the
> corresponding version of CPython, JPython uses .class files.
> Python.NET is MS vapour, so I have no idea what it uses.
This isn't really restricted to .pycs -- the point is that a package
cann
On 10 Jan 2001 10:07:16 -0600, Rob Tillotson <[EMAIL PROTECTED]> wrote:
> > (Does anyone know where the bytecode format is documented? I am
> > interested in understanding how bytecode works and is designed.)
>
> As far as I know it's only documented in the source. The standard
> module "dis.py
On 10 Jan 2001 09:16:51 -0600, Rob Tillotson <[EMAIL PROTECTED]> wrote:
> Python 1.5 and 2.0 --- there is also jpython, stackless, perhaps
> even python.net, and it might eventually be desirable to have all of
> these installed side-by-side with separate sets of library modules.
Only CPython uses
On Tue, 9 Jan 2001 21:03:57 +0100, [EMAIL PROTECTED] wrote:
> From the Python news file:
> - Python bytecode files (*.pyc and *.pyo) are not compatible between
> releases.
Note that this is a promise the Python development team makes :
we break the .pyc almost every revision. In particular 2.1 (w
4 matches
Mail list logo
