➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author geon
Recipients geon, loewis
Date 2009-01-03.15:08:22
SpamBayes Score 0.005205327
Marked as misclassified No
Message-id <1230995303.87.0.918540869956.issue4815@psf.upfronthosting.co.za>
In-reply-to
Content 
seems to be working.

Seems to me now I get it. The file encoding is ruled by the encoding
declaration. When I stated 

# -*- coding: cp1250 -*-

then the file would be saved in cp1250. 

Now hoping that I would keep this issue, cause it comes with this
patches: when I open file *with* say # -*- coding: cp1250 -*-, I am
asked to change to utf8. This behaviour was not before and is probably
unwanted.....
History
Date User Action Args
2009-01-03 15:08:24geonsetrecipients: + geon, loewis
2009-01-03 15:08:23geonsetmessageid: <1230995303.87.0.918540869956.issue4815@psf.upfronthosting.co.za>
2009-01-03 15:08:23geonlinkissue4815 messages
2009-01-03 15:08:22geoncreate