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 ezio.melotti
Recipients [PhysiC], ezio.melotti
Date 2009-07-28.13:00:27
SpamBayes Score 0.000175144
Marked as misclassified No
Message-id <1248786029.7.0.290114698849.issue6590@psf.upfronthosting.co.za>
In-reply-to
Content
This looks more like a general question than a bug report. You should
probably ask on comp.lang.python or #python@irc.freenode.net.

The "# -*- coding: cp1254 -*-" only specifies the encoding used to save
the source file and it's not related to the encoding used when the data
are printed or sent over the network. This should be the same for both
Py2 and Py3.
The browser determines the encoding reading it from the HTTP headers,
from the content-type in the HTML <meta> tag or from the XML
declaration. If none of these are available it tries to determine it
from the content of the file. You should probably specify the encoding
in the headers and encode the data you send accordingly.

Closing as invalid.
History
Date User Action Args
2009-07-28 13:00:29ezio.melottisetrecipients: + ezio.melotti, [PhysiC]
2009-07-28 13:00:29ezio.melottisetmessageid: <1248786029.7.0.290114698849.issue6590@psf.upfronthosting.co.za>
2009-07-28 13:00:28ezio.melottilinkissue6590 messages
2009-07-28 13:00:27ezio.melotticreate