Re: 2nd try: python 2.0

2000-11-28 Thread Tony Seward
On 28 Nov 2000, Thilo Mezger wrote: > Tony Seward <[EMAIL PROTECTED]> wrote: > > I'd like to start using the Unicode support but I can deal without it for > > now. Same for list comprehensions. > > Install Python 2.0 in /usr/local and call it with > > #!/usr/bin/env python2 > Yes, I've

Re: 2nd try: python 2.0

2000-11-27 Thread Thilo Mezger
Tony Seward <[EMAIL PROTECTED]> wrote: > I'd like to start using the Unicode support but I can deal without it for > now. Same for list comprehensions. Install Python 2.0 in /usr/local and call it with #!/usr/bin/env python2 or something like this. I just have to agree that upgrading

Re: 2nd try: python 2.0

2000-11-27 Thread Tony Seward
I'd like to start using the Unicode support but I can deal without it for now. Same for list comprehensions. I plan on wrapping a C++ library with the ExtensionClass module, so the improved suppor would be nice. Again, I can wait. The Numeric module requires distutils, so I need either Python

Re: 2nd try: python 2.0

2000-11-27 Thread Matt Wilson
All C python modules are binary incompatible with 2.0. It will take quite some time to work out all the problems there. What wins are in 2.0 that you really need? Matt On Mon, Nov 27, 2000 at 10:21:27AM -0700, Tony Seward wrote: > I'm reposting because I didn't get a response the first time. >

2nd try: python 2.0

2000-11-27 Thread Tony Seward
I'm reposting because I didn't get a response the first time. Is there a timetable for moving to python 2.0 in rawhide? Are there any outstanding compatibility issues that need to be resolved first? Tony ___ Redhat-devel-list mailing list [EMAIL P