See subject. I am really worry, before putting more effort to it, can any body explain the current status of python 2? Unicode is a must for my work, without it, python is useless. So I need python 2, if 2.0 will die, I better switch beforehand. Sorry!!! but it is very important. Rgs, Kent Sin --------------------------------- kentsin.weblogs.com kentsin.imeme.net
Sin Hang Kin wrote:
See subject. I am really worry, before putting more effort to it, can any body explain the current status of python 2?
In short: no way ;-) For the long story read on here: http://www.pythonlabs.com/tech/python2.html http://www.pythonlabs.com/tech/ http://www.pythonlabs.com/plans.html
Unicode is a must for my work, without it, python is useless. So I need python 2, if 2.0 will die, I better switch beforehand.
Python2 has native Unicode support -- probably one of the most advanced there currently is among scripting languages. -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
On Mon, Jul 17, 2000 at 09:30:16PM +0800, Sin Hang Kin wrote:
I am really worry, before putting more effort to it, can any body explain the current status of python 2? Unicode is a must for my work, without it, python is useless. So I need python 2, if 2.0 will die, I better switch beforehand.
Sorry!!! but it is very important.
You betcha it's important ! What do those five people at PythonLabs do when Python dies ? They'd be out of a job ! Can't have that, now can we ;) Seriously, though: Python is not dead. Python 2 is not dead. CNRI and BeOpen are trying to resolve some 'issues', and the last news is that CNRI is going to release Python 1.6. I assume it'll be based off the 1.6 alphas, and those included unicode. BeOpen / PythonLabs will probably start by releasing Python 2.0. This'll likely have to wait until 1.6 is released, but the python dev team is working hard to make 2.0 a complete release on its own. It will include unicode, probably with less bugs and problems than 1.6 ;-) It will also include a ton of other things, which are being worked on right now. (Some of the things that might be included in 2.0 are list comprehensions (a way to replace map, filter and reduce), augmented assignment (x += y and such), online help() facility for the interpreter, possibly some new library modules, and many enhancements to the current standard library.) However, because of the issues between CNRI and BeOpen, it's completely unclear when Python 2.0 will be released. (Or, indeed, when CNRI's Python 1.6 will be released.) If you need the unicode support now, I'd suggest grabbing the CVS tree and see how it suits your needs. If it doesn't, give people here some feedback, so they can fix the problems or suggest ways to work around it. There are likely to be some changes to unicode (the functionality of '\x' and '\u' for instance) but the code is pretty solid as it is. Hope that helps ;) -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
Python cannot die while its license permits anyone to improve it and there are still thousands of users. If Python were in any danger, there are dozens of people who could take over its advancement, including its current maintainer, Guido, at his new job! -- Paul Prescod - Not encumbered by corporate consensus It's difficult to extract sense from strings, but they're the only communication coin we can count on. - http://www.cs.yale.edu/~perlis-alan/quotes.html
Paul Prescod wrote:
Python cannot die while its license permits anyone to improve it and there are still thousands of users. If Python were in any danger, there are dozens of people who could take over its advancement, including its current maintainer, Guido, at his new job!
Tim once (0.9-winking-ly) mentioned the possibility of voting with the "keyboard by grabbing the Python source and making your own release". I don't wanna do this on my own (and get zapped from a lightning bolt thrown by the powers that are), but what would be the pros and cons of an inofficial (maybe 1.8?) alpha-in-between-release? I think the CVS tree is in a relative stable state, so if this is going to take another 1 1/2 months, this might be a good time. just-thinking-and-winking-ly y'rs Peter -- Peter Schneider-Kamp ++47-7388-7331 Herman Krags veg 51-11 mailto:peter@schneider-kamp.de N-7050 Trondheim http://schneider-kamp.de
Peter Schneider-Kamp wrote:
...
Tim once (0.9-winking-ly) mentioned the possibility of voting with the "keyboard by grabbing the Python source and making your own release".
As long as Tim and Guido are thinking about this possibility, I don't want to waste my brain cells considering it. I don't have as much information as they do and I'm only a little bit smarter than them anyhow. :) Seriously, I don't know enough about the licensing issues. I don't know exactly what CNRI "owns" and what we need from them to proceed. -- Paul Prescod - Not encumbered by corporate consensus It's difficult to extract sense from strings, but they're the only communication coin we can count on. - http://www.cs.yale.edu/~perlis-alan/quotes.html
On Mon, Jul 17, 2000 at 01:21:25PM -0500, Paul Prescod wrote:
Peter Schneider-Kamp wrote:
I don't have as much information as they do and I'm only a little bit smarter than them anyhow. :)
Yeah, I'm only a little bit smarter than Guido divided by Tim, too. Or-is-that-Guido-minus-Tim-ly y'rs, ;) -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
[Peter Schneider-Kamp]
Tim once (0.9-winking-ly) mentioned the possibility of voting with the "keyboard by grabbing the Python source and making your own release".
I don't wanna do this on my own (and get zapped from a lightning bolt thrown by the powers that are), but what would be the pros and cons of an inofficial (maybe 1.8?) alpha-in-between-release?
I don't see any pros at this time, although I'm typing on my laptop while sitting on the sidewalk in the dark in front of a Howard Johnson's with my hair dripping wet, so Guido can sleep in peace in the room we're sharing, and this after a hellish 12-hour trip to get to the God-forsaken State of California, so I'm not seeing many pros of any kind at the moment <wink>. The Python Consortium meeting is this Friday, and the license hassles are on the agenda. While not privy to all the details myself, I can't imagine that any side in this debate can afford to *allow* the impasse to continue longer than that. So I'd advise a bit more patience. I intend to stay all up night, listening for secrets Guido may spill in his sleep. the-con-is-making-a-confused-release-even-more-confused-ly y'rs - tim
On Tue, 18 Jul 2000, Tim Peters wrote:
[Peter Schneider-Kamp]
Tim once (0.9-winking-ly) mentioned the possibility of voting with the "keyboard by grabbing the Python source and making your own release".
I don't wanna do this on my own (and get zapped from a lightning bolt thrown by the powers that are), but what would be the pros and cons of an inofficial (maybe 1.8?) alpha-in-between-release?
I don't see any pros at this time
I agree with Tim -- your 1.8 would face backwards- and forwards- compatabilitiy issues CVS versions do not have to face.
, although I'm typing on my laptop while sitting on the sidewalk in the dark in front of a Howard Johnson's with my hair dripping wet, so Guido can sleep in peace in the room we're sharing, and this after a hellish 12-hour trip to get to the God-forsaken State of California, so I'm not seeing many pros of any kind at the moment <wink>.
Sounds like loads of fun....next you should get into the room and wake up Guido. That should be even more fun.
So I'd advise a bit more patience. I intend to stay all up night, listening for secrets Guido may spill in his sleep.
I don't think you should. there-are-some-things-bots-were-not-meant-to-know-ly y'rs, Z. -- Moshe Zadka <moshez@math.huji.ac.il> There is no GOD but Python, and HTTP is its prophet. http://advogato.org/person/moshez
Moshe Zadka wrote:
I agree with Tim -- your 1.8 would face backwards- and forwards- compatabilitiy issues CVS versions do not have to face.
I basically agree. An official release would be a Bad Thing(TM). But at least some information should leak to the masses to prevent slashdot threads like that: http://slashdot.org/comments.pl?sid=00/07/17/0312221&threshold=-1&commentsort=0&mode=flat&cid=41 Peter -- Peter Schneider-Kamp ++47-7388-7331 Herman Krags veg 51-11 mailto:peter@schneider-kamp.de N-7050 Trondheim http://schneider-kamp.de
On Tue, 18 Jul 2000, Peter Schneider-Kamp wrote:
But at least some information should leak to the masses to prevent slashdot threads like that:
http://slashdot.org/comments.pl?sid=00/07/17/0312221&threshold=-1&commentsort=0&mode=flat&cid=41
My fault -- I stopped reading /. Can you summarize the thread? -- Moshe Zadka <moshez@math.huji.ac.il> There is no GOD but Python, and HTTP is its prophet. http://advogato.org/person/moshez
Moshe Zadka wrote:
My fault -- I stopped reading /. Can you summarize the thread?
The thread is about if Visual Python is an alternative for Visual Basic or, if not, it can be used as that. A subthread of this thread dealt with Pythons release schedule: "Speaking of Python, does anyone know what's up with Python 1.6^H^H2.0? A while back, python.org had said that version 1.6 would be out on June 1. Then there was an announcement, mid-June that it would be delayed. Then at the end of June, this link was placed on python.org, and it was stated that the Python interpreter, version 1.6, was renamed to 2.0, and the first beta would be available on July 1. Now, on July 17, that link has been removed from python.org (although the webpage still exists), and the release schedule is gone!" Quoting from relevant replies: "python 1.6 will be out in august check the downloads page of www.python.org or checkout the pythonlabs at www.beopen.com where most of the core python developers opened shop" "Yeah, the Python 1.6 download page says that Python 1.6 beta1 will be done on July 1, and beta 2 on July 14. It's July 17 now, and the only available download is alpha 2...." read-what-you-want-from-that-ly y'rs Peter -- Peter Schneider-Kamp ++47-7388-7331 Herman Krags veg 51-11 mailto:peter@schneider-kamp.de N-7050 Trondheim http://schneider-kamp.de
Peter Schneider-Kamp wrote:
Moshe Zadka wrote:
My fault -- I stopped reading /. Can you summarize the thread?
The thread is about if Visual Python is an alternative for Visual Basic or, if not, it can be used as that.
A subthread of this thread dealt with Pythons release schedule: "Speaking of Python, does anyone know what's up with Python 1.6^H^H2.0? A while back, python.org had said that version 1.6 would be out on June 1. Then there was an announcement, mid-June that it would be delayed. Then at the end of June, this link was placed on python.org, and it was stated that the Python interpreter, version 1.6, was renamed to 2.0, and the first beta would be available on July 1. Now, on July 17, that link has been removed from python.org (although the webpage still exists), and the release schedule is gone!"
Quoting from relevant replies: "python 1.6 will be out in august check the downloads page of www.python.org or checkout the pythonlabs at www.beopen.com where most of the core python developers opened shop"
"Yeah, the Python 1.6 download page says that Python 1.6 beta1 will be done on July 1, and beta 2 on July 14. It's July 17 now, and the only available download is alpha 2...."
You may not have noticed, but the 2.0beta1 is already available to the public: just download the most recent CVS version (or the tarball from David Ascher's starship page). About the schedule: I think we'll know more after the Python Consortium Meeting. -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
Tim Peters wrote:
I don't see any pros at this time, although I'm typing on my laptop while sitting on the sidewalk in the dark in front of a Howard Johnson's with my hair dripping wet, so Guido can sleep in peace in the room we're sharing, and this after a hellish 12-hour trip to get to the God-forsaken State of California, so I'm not seeing many pros of any kind at the moment <wink>.
<insert("BIG GRIN")>
The Python Consortium meeting is this Friday, and the license hassles are on the agenda. While not privy to all the details myself, I can't imagine that any side in this debate can afford to *allow* the impasse to continue longer than that.
Okay, that sounds better than nothing. Meanwhile the question "what happened to 1.6?" starts popping up in c.l.py more often.
So I'd advise a bit more patience. I intend to stay all up night, listening for secrets Guido may spill in his sleep.
Be sure to write a secret transcript of *everything*. We might use it the next time we want to add some special syntax to Python<wink> being-more-patient-ly y'rs Peter -- Peter Schneider-Kamp ++47-7388-7331 Herman Krags veg 51-11 mailto:peter@schneider-kamp.de N-7050 Trondheim http://schneider-kamp.de
participants (7)
-
M.-A. Lemburg -
Moshe Zadka -
Paul Prescod -
Peter Schneider-Kamp -
Sin Hang Kin -
Thomas Wouters -
Tim Peters