On Tue, Aug 30, 2011 at 11:34 AM, stefan brunthaler <ste...@brunthaler.net> wrote: >> Um, I'm sorry, but that reply sounds incredibly naive, like you're not >> really sure what the on-disk format for .pyc files is or why it would >> matter. You're not even answering the question, except indirectly -- >> it seems that you've never even thought about the possibility of >> generating a .pyc file on one platform and copying it to a computer >> using a different one.
> Well, it may sound incredibly naive, but the truth is: I am never > storing the optimized representation to disk, it's done purely at > runtime when profiling tells me it makes sense to make the switch. > Thus I circumvent many of the problems outlined by you. So I am > positive that a full fledged change of the representation has many > more intricacies to it, but my approach is only tangentially > related... Ok, there there's something else you haven't told us. Are you saying that the original (old) bytecode is still used (and hence written to and read from .pyc files)? -- --Guido van Rossum (python.org/~guido) _______________________________________________ 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
