Fredrik> byte code is portable between platforms, but it's not portable
Fredrik> between different major Python releases (2.4.2 can run 2.4.1
Fredrik> bytecodes, but not 2.3 bytecodes, etc).
There is one slight problem with transporting .pyc files. The generated
.pyc file records the
Shobha Rani wrote:
(I think more people might read your posts if you skip the HTML stuff;
if you insist on HTML, you could at least use a reasonable color)
> How byte code is generated? For example when we run the java
> program then the compiler generates the byte code?
> How the byte code is ge
How
byte code is generated? For example when we run the java program then the
compiler generates the byte code?
How
the byte code is generated for the source code(java)?
Regards,
Shobha Rani @
Genesis
--
http://mail.python.org/mailman/listinfo/python-list
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
10 matches
Mail list logo
