git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Third try at documenting command integration requirements.

From
Eric S. Raymond <esr@thyrsus.com>
Date
Nov 28, 2012, 03:36 UTC
Message-ID
<20121128033639.GC1669@thyrsus.com>
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>
Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 10 in “Third try at documenting command integration requirements.”
  1. Third try at documenting command integration requirements.Eric S. Raymond, Nov 26, 2012
  2. Perry HutchisonNov 26, 2012
  3. Junio C HamanoNov 26, 2012
  4. Eric S. RaymondNov 26, 2012
  5. Michael HaggertyNov 27, 2012
  6. Eric S. RaymondNov 27, 2012
  7. Junio C HamanoNov 28, 2012
  8. Eric S. RaymondNov 28, 2012
  9. Junio C HamanoNov 26, 2012
  10. Eric S. RaymondNov 26, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.