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 jh45
Recipients docs@python, eric.araujo, jh45, vstinner
Date 2011-07-06.05:48:03
SpamBayes Score 0.002036417
Marked as misclassified No
Message-id <1309931284.78.0.0691809483413.issue11230@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry for the long delay.

haypo wrote:
  Can you propose a sentence which is more clear about bytes/Unicode?

On this page:
http://www.python.org/download/releases/3.2/
is this line:
"- countless fixes regarding bytes/string issues; among them full support for a bytes environment (filenames, environment variables)"

How about adding to that line something like:
" on UNIX; but on Windows the path to and name of each module you import can contain only characters that are in the ANSI codepage that your Windows is using"

and maybe
" (will be fixed in Python 3.3)"

and maybe (or not) also something like:
" (ANSI codepage = basic latin + other characters of only your own language group)"

-- jh
History
Date User Action Args
2011-07-06 05:48:04jh45setrecipients: + jh45, vstinner, eric.araujo, docs@python
2011-07-06 05:48:04jh45setmessageid: <1309931284.78.0.0691809483413.issue11230@psf.upfronthosting.co.za>
2011-07-06 05:48:04jh45linkissue11230 messages
2011-07-06 05:48:03jh45create