On 11/4/09, ssteinerX at gmail.com <ssteinerx at gmail.com> wrote: > Maybe the 3.x line should just be put out of our misery, merged back > to 2.7, 2.8, 2.9, and proceed as Glyph suggested in passing with > increasing levels of deprecation until it just turns into 3.x on its > own by running out of numbers. <delurk> As a user, I'm horrified. Granted, I'm not the most high powered user, but . . . my employer is already providing me with a 3.0 Python version on one of my work computers with the expectation that I'll be using it more and more. Sorry to butt in, but is this a joke? I thought all this was hashed out prior to inventing python 3.0. </delurk>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4