>> It won't work in this case. Compilation of the module might well
>> fail because of Python2/Python3 syntax differences.
Leif> Well, then this isn't something to be implemented for python 2,
Leif> it's something to consider for python 3 and greater.
It won't work there either. It's quite possible that a module written for
Python 2 won't compile under Python 3. Compilation is currently the only
route to execution. You'd have to come up with some other scheme. Someone
suggested something akin to a "from __future__" facility or the #! trick you
and others mentioned, but that would only work for Python 2.6 and above.
Skip
_______________________________________________
Python-3000 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
