[Python-Dev] Python Consortium Meeting News

Asbahr, Jason Jasbahr@origin.EA.com
Mon, 24 Jul 2000 12:07:58 -0500

Depending on the release schedule for 2.0, we may have to ship our 
product with Python 1.6, and Unicode is one of the key features we
need from this release.  I hope Marc is right that the current 
version of the Unicode support can be incorporated into the 1.6
official release.


Jason Asbahr
Origin Systems, Inc.

-----Original Message-----
From: M.-A. Lemburg [mailto:mal@lemburg.com]
Sent: Monday, July 24, 2000 10:29 AM
To: akuchlin@mems-exchange.org
Cc: python-dev@python.org
Subject: Re: [Python-Dev] Python Consortium Meeting News

Andrew Kuchling wrote:
> On Sat, Jul 22, 2000 at 01:41:03PM -0400, Tim Peters wrote:
> >since 1.5.2 was released to the public".  The great recent burst of
> >Python-Dev activity in the CVS tree was not done at CNRI, or the bulk of
> >even by people with any connection present or past to CNRI.
> The problem there is Unicode support, which has changed quite a bit
> since that time -- the default encoding, if nothing else.  1.6 will
> probably need to have Unicode disabled, or have support that's
> incompatible with 2.0, or someone will have to backport the current
> code to 1.6. (Better you guys than me, though...)

Hmm, why shouldn't it be possible to use the current
version of Unicode support in 1.6 ? AFAIK, most of the patching
was done by Fredrik and myself and we were not related to
CNRI or BeOpen in any way at the time of the move to BeOpen.

Wouldn't it suffice for Fredrik and me to send in a wet-sign
for the Unicode patches since that date ?

Marc-Andre Lemburg
Business:                                      http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/

Python-Dev mailing list