On Sun, Jun 20, 2010 at 5:55 AM, Simon de Vlieger <simon at ikanobori.jp> wrote: > As for the potentially harmful text on Python 3 which is included on the > python-commandments website I do get the hint that it might not be clear > enough that the text does not apply to people who are porting libraries. > This is a complaint I have heard before and to which I will take affirmative > action by explicitly adding text to clarify that. I just read that page, and I believe it could do with a little refinement even from an application developer point of view. Specifically, rather than "Why shouldn't I use it, yet?", a more positive phrasing would be "Should I use it, yet?" or "Is Python 3 ready for me, yet?". And then suggest to app developers that they check the status of Py3k support for libraries they need or think they will need, as these days many of them will provide a 3.x compatible version. Staying on 2.x for now is certainly a viable choice - there's a reason that backports to 2.7 have been a prominent python-dev activity for the last year or two. With that nearly out the door, the focus will switch more to Py3k. Cheers, Nick. P.S. wind the clock back 12 months or so, and I think the page as it currently stands would have been perfectly good advice to app developers. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
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