Serhiy Storchaka added the comment:
Most of changes are applicable to Python 2 too. Do you want backport part of
your patch to 2.7?
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
Roundup Robot added the comment:
New changeset 1dbbed06a163 by Andrew Kuchling in branch '3.3':
#4153: update Unicode howto for Python 3.3
http://hg.python.org/cpython/rev/1dbbed06a163
--
___
Python tracker rep...@bugs.python.org
A.M. Kuchling added the comment:
As far as I can tell, there are no other outstanding suggestions for howto
updates, so I'll now close this item. Feel free to re-open or file a new item
if there are further improvements that can be made.
--
resolution: - fixed
stage: commit review -
A.M. Kuchling added the comment:
Continuing my tour of the howtos, here's a patch making many of the changes
discussed here and on issue13997. Changes made:
* state that python3 source encoding is UTF-8, and give examples
* mention surrogateescape in the 'tips and tricks' section, and
A.M. Kuchling added the comment:
Updated version of my patch, which adds two more todo items and handles Ezio's
review comments:
* Switch from Greek examples to French, and remove non-Latin-1 characters.
* Change language for bytes.decode to but supports a few more possible
handlers.
*
Nick Coghlan added the comment:
amk's latest patch looks like a very nice improvement to me.
One suggested wording tweak for the aside about the simplified
history: s/The average Python programmer doesn't need to know the
historical details/The precise historical details aren't relevant to
Ezio Melotti added the comment:
As discussed in #13997, the HOWTO should be reorganized to start with a basic
introduction and then expand on more advanced topic.
See also msg180743 for a couple of essays that could be linked as see also or
integrated in the HOWTO.
--
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
___
___
Python-bugs-list
Nick Coghlan added the comment:
The section in the HOWTO on Python's unicode support also misses the fact that
the easiest way to include a Unicode character in a string literal in Python 3
is to *include that character in the string literal* (since source code is now
treated as UTF-8 by
Roundup Robot added the comment:
New changeset 260a9afd999a by Ezio Melotti in branch '3.2':
#4153: update the Unicode howto.
http://hg.python.org/cpython/rev/260a9afd999a
New changeset 572ca3d35c2f by Ezio Melotti in branch '3.3':
#4153: merge with 3.2.
Ezio Melotti added the comment:
I committed the attached patch with some minor modifications, but there are
still comments that should be addressed on Rietveld.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
assignee: - ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
___
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
___
___
Python-bugs-list
Éric Araujo mer...@netwok.org added the comment:
something about Unicode supports in the re module (this probably can
wait after the 'regex' inclusion).
I’d prefer documentation for the re module now.
--
___
Python tracker rep...@bugs.python.org
Éric Araujo mer...@netwok.org added the comment:
it also removes the usage of 'byte string'.
I see you’ve replaced it with “byte object”. I’m -0, as “byte[s] string” is
not ambiguous IMO.
--
___
Python tracker rep...@bugs.python.org
Ezio Melotti ezio.melo...@gmail.com added the comment:
There was some discussion a while ago on python-dev about it. AFAIR the
outcome was that using bytes *strings* should be avoided because bytes are
bytes, and not strings (until they get decoded at least). Using 'string' for
both might
Éric Araujo mer...@netwok.org added the comment:
Ah, I see: you’re equating “string” with “text string” or “character string”,
whereas I read “bytes string” as “finite sequence of bytes”. With this
definition, there *are* two string types in Python 3, it’s just that they’re
much more
Ezio Melotti ezio.melo...@gmail.com added the comment:
After the recent discussions on python-dev I went through the Unicode howto and
fixed a few things, then I found this issue so I'm attaching the patch here.
The patch addresses mostly markup issues, but it also removes the usage of
'byte
Ezio Melotti ezio.melo...@gmail.com added the comment:
I also left a few comments on rietveld about other things that can be improved.
Please reply and comment there.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
Committed in revision 86530. Thanks Terry and Raymond for your comments. I
would like to keep this issue open (at a low priority) because the question in
the titles is still relevant. There are many new 3.x features
Éric Araujo mer...@netwok.org added the comment:
Agreed on 1 and 3. Regarding 2, looking at the early history of the file makes
me suspect that amk is the author.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
Changes by Alexander Belopolsky belopol...@users.sourceforge.net:
Added file: http://bugs.python.org/file19632/issue4153.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
___
Changes by Alexander Belopolsky belopol...@users.sourceforge.net:
Removed file: http://bugs.python.org/file19631/issue4153.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
___
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
r82301 appears to be a blind merge of r82120 from the trunk. It is fairly
obvious that it was not intentional.
--
___
Python tracker rep...@bugs.python.org
Changes by Alexander Belopolsky belopol...@users.sourceforge.net:
--
nosy: +akuchling
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
___
___
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
___
___
Python-bugs-list
Terry J. Reedy tjre...@udel.edu added the comment:
Thanks for persisting with this. Looking at the patch:
@@ -65,7 +63,7 @@
goal was to have Unicode contain the alphabets for every single human language.
It turns out that even 16 bits isn't enough to meet that goal, and the modern
Unicode
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
___
___
Python-bugs-list
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
On Thu, Nov 18, 2010 at 2:41 PM, Terry J. Reedy rep...@bugs.python.org wrote:
..
I visually parse 0-1,114,111 as 0-1, 114, 111. So I think either the commas
should be removed or extra spaces are needed: 0-1114111 or 0 -
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
On Thu, Nov 18, 2010 at 3:00 PM, Alexander Belopolsky
rep...@bugs.python.org wrote:
..
I really think of them as hex or hexadecimal digits, just as 0-9 are
decimal, not base 10 digits.
I am fine with hexadecimal here.
Terry J. Reedy tjre...@udel.edu added the comment:
0 through ... is fine with me.
Yes, hex numeral would be more accurate than hex digit.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4153
Raymond Hettinger rhettin...@users.sourceforge.net added the comment:
Yes, hex numeral would be more accurate than hex digit.
Stick with hex digit. We've used that phraseology for a long time. See
string.hexdigits for example. And hex numeral just sounds weird -- it makes
me do a
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
Reopening because it looks like the fix was reverted in r82301.
This HOWTO discusses Python 2.x’s support for Unicode, and explains various
problems that people commonly encounter when trying to work with Unicode. (This
Georg Brandl [EMAIL PROTECTED] added the comment:
Thanks for noting this! The most basic changes had been done, but I had
to revise some sections for changes. Done in r67338.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL
34 matches
Mail list logo
