Hi Luca,
On Feb 26, 2010, at 12:41 AM, Luca wrote:
MRAB wrote:
Perhaps you could use a different extension, eg ".pyn", so existing
".py" files are handled as-is but ".pyn" files are read through a
translator.
This could be a good idea... especially since i could make my own
extension since we are talking of a special-purpose application that
only incorporates python as a library.
I would suggest to do choose the same strategy as 'from __future__
import ...' takes, which does similar things and limits them to the
module it is used in. I would be curious to hear about your results.
Kind regards, Roald
--
http://mail.python.org/mailman/listinfo/python-list