2.3 encoding parsing bug
Edward K. Ream
edreamleo at charter.net
Tue Feb 17 23:27:39 EST 2004
> Presumably it would also work if you just included a pair of blank
> lines
Inserting two blanks lines to defeat the encoding convention would be very
bad programming style. Instead of blank lines I would insert:
# first line to defeat Python's encoding convention.
# second line to defeat Python's encoding convention.
Naturally, this is hardly an improvement over a line that explicitly
specifies the encoding.
Regardless of various workarounds, the essence of this situation is that pep
263 drastically changed the Python language. Indeed, it invalidated a file
format that I as an application designer should have had the right to
define, and _did_ have the right to define until Python 2.3 interfered. I
am not happy.
Edward
--------------------------------------------------------------------
Edward K. Ream email: edreamleo at charter.net
Leo: Literate Editor with Outlines
Leo: http://webpages.charter.net/edreamleo/front.html
--------------------------------------------------------------------
More information about the Python-list
mailing list