By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,675 Members | 2,270 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,675 IT Pros & Developers. It's quick & easy.

Re: Python and Flaming Thunder

P: n/a
On May 28, 11:46 pm, Dave Parker <>
On May 28, 3:19 pm, "Diez B. Roggisch" <de...@nospam.web.dewrote:
Kind of like how this year's program won't work on next year's
"Like Perl 6, Python 3.0 will break backward compatibility. There is
no requirement that Python 2.x code will run unmodified on Python 3.0..
See? 2.x -3.x. Major version. Not "next week's python", not "next year's
python", but "the next mayor version of python". With a clean, well documented,
upgrade path.

Unlike "next month's Flaming Thunder". (Unless you are producing a new major
version every week, in which case I shut up, and may think about buying several
versions only so you must keep maintaining all of them)

Luis Zarrabeitia
Facultad de Matemática y Computación, UH

Jun 27 '08 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.