Philippe C. Martin wrote:
> I understand from my reading that a .pyc generated by python anywhere
> should run anywhere else - is that true ?
>
> If I generate 'compile.all' a pyc with python 2.3.3 under Linux, I
^
> get a 'bad magic number' try
Fredrik Lundh wrote:
AFAIK, they *are* platform dependent. You can not share pyc files between ASCII and EBCDIC
machine.
however, that could be seen as be a flaw in the EBCDIC ports.
We'll see if this could be fixed. I try to foster some "movement" in
Python/400 (I love this name, please, dont ca
Jarek Zgoda wrote:
> AFAIK, they *are* platform dependent. You can not share pyc files between
> ASCII and EBCDIC
> machine.
however, that could be seen as be a flaw in the EBCDIC ports.
--
http://mail.python.org/mailman/listinfo/python-list
Aaron Bingham wrote:
.pyc files are platform-independant but are incompatible between major
Python versions. You can not use a .pyc file generated with Python 2.3
with Python 2.4 or vice versa.
AFAIK, they *are* platform dependent. You can not share pyc files
between ASCII and EBCDIC machine.
> I understand from my reading that a .pyc generated by python anywhere should
> run anywhere else - is that true ?
> If I generate 'compile.all' a pyc with python 2.3.3 under Linux, I get a 'bad
> magic number' trying to execute it under windows (2.4).
> What am I doing wrong ?
You should use the
Philippe C. Martin wrote:
I understand from my reading that a .pyc generated by python anywhere should
run anywhere else - is that true ?
If I generate 'compile.all' a pyc with python 2.3.3 under Linux, I get a 'bad
magic number' trying to execute it under windows (2.4).
What am I doing wrong ?
Hi,
I understand from my reading that a .pyc generated by python anywhere should
run anywhere else - is that true ?
If I generate 'compile.all' a pyc with python 2.3.3 under Linux, I get a 'bad
magic number' trying to execute it under windows (2.4).
What am I doing wrong ?
are the pyc platef
