From: "Eric S. Raymond" <esr@thyrsus.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>, git@vger.kernel.org
Subject: Re: [PATCH] Third try at documenting command integration requirements.
Date: Tue, 27 Nov 2012 22:36:39 -0500 [thread overview]
Message-ID: <20121128033639.GC1669@thyrsus.com> (raw)
In-Reply-To: <7vobiijxol.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com>:
> I won't worry about Python 3 yet; in what timeframe did Python's
> i18n/unicode support become usable? In 2.4, or 2.6?
Er, it depends on what you consider "usable".
Unicode integration turned out to have a lot messier edge cases than
anyone understood going in. First-cut support was in 1.6, but I'd say
it still has some pretty sharp edges *today*. Which is why 3.0 has
gone all-Unicode-all-the-time. The problems mostly come from having
two different notions of "string" that don't really mix well.
Me, I still avoid the hell out of Unicode in Python. And occasionally
fund myself cursing a library maintainer who didn't.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2012-11-28 3:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 5:35 [PATCH] Third try at documenting command integration requirements Eric S. Raymond
2012-11-26 8:07 ` Perry Hutchison
2012-11-26 20:01 ` Junio C Hamano
2012-11-26 21:41 ` Eric S. Raymond
2012-11-27 11:49 ` Michael Haggerty
2012-11-27 17:56 ` Eric S. Raymond
2012-11-28 1:58 ` Junio C Hamano
2012-11-28 3:36 ` Eric S. Raymond [this message]
2012-11-26 21:41 ` Junio C Hamano
2012-11-26 22:01 ` Eric S. Raymond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121128033639.GC1669@thyrsus.com \
--to=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.