Re: [Python-Dev] Python Library Support in 3.x (Was: email package status in 3.X)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, Sorry for the maybe somewhat late response but I am not a subscriber on the python-dev mailinglists. Someone else pointed me towards this thread and I want to shortly clarify a few things regarding the following two statements:
It is not "critical self-evaluation" to repeat "Python 3 is not ready" as litany in #Python and your supporting website. I use the word "litany" here because #Python refers users to what appears to be a religious website http://python-commandments.org/python3.html
python-commandments.org is owned and hosted by the same person (Allen Short aka dash aka washort) as pound-python.org which is the "official" website for #Python and which links to it.
Both python-commandments.org and pound-python.org are my websites. I own both the domains and I do all administrative tasks regarding these domains. pound-python.org is the official #python website and as such is maintained on Launchpad by a team of volunteers, see: https://launchpad.net/ ~pound-python which is indeed owned by Allen Short. However, Allen Short has nothing to do with the Python Commandments page. That is an endeavor for which I am the sole responsible person. I have asked some people to contribute texts but that doesn't change that I should be spoken to regarding the content on that website. If there are any issues with the content on either website please do not hesitate to contact me at this email address or on IRC where I go by the nickname of ikanobori. 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. Hope all is well, Regards, Simon de Vlieger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQIcBAEBAgAGBQJMHSC2AAoJEBBSHP7i+JXf5pMQANPBCUzDwx2xjTP8shA1E4mx 7/OQk27nxt+wOZNT0Ybe/iNXLetF6qa8At7kTau/yU3l/xJWVODjfJUICkDv/0ad ebMKiFeKO8jqdvEe+RL3ck7jTXEM73C2PLNtge9FLTY6HhYrXnOJakNbpWPJR/PG TQQ+mY/8ZvSP+n98RrY9kcVaVJMSmXUJWHvWVh+LkcIDwF/h30EH/e5PUGzylINI NiV5955pNRXTnwdgjsouljUI/rrod3zphnUEyL22QvSUx0b7YXMfC24eRGTpwrLg 9cyQAMjjbuVqkhSJhYFnm+DKwsZEAHxxOvu50Xwuy3i1C7c8L6/QDT1txoSTVuaP 4xw8GSFEblbHviz7hY7KCe5nMpBNHNfcGFHFSWd+WYogRXjpDitlMDNW8HT56pRW lwzs1WENnoOSCAn4Xds+xPJj9JyAGnS8rWz70RVMyrkHDFaJhDlIDNpEFdlAlywT R0uCQrlxs/uWzAXK2IA0wXPtm/m8fYLR3q8mD4++QotZKQcT4ciN7Xv913/ZT2b2 NtR1WEoTZAV+gWrFyFsgmMFAmZhvUdI8Ludxs3l2smHHaCFUkj2Ur9BrkMiEv5Z8 wLN+/LRaHgGnmVT2SF0LOCeOLz97dP728OKBO0DwxqT89Cla8445z7ktdHnJ3amA gjbsfG7W+yx9L2v0IDFC =YDiR -----END PGP SIGNATURE-----
Simon de Vlieger writes:
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.
It also doesn't apply to people who don't need unported libraries, eg, where the task is plain old text filtering or command line scripting. Don't ask me for the list of "unported libraries", I know of none from personal experience.<wink> You might also want to withdraw the claim that Python 2.x is actively developed. With the release of 2.7, that's not true any more, not in the sense that most people think of "actively developed."
On Sun, Jun 20, 2010 at 5:55 AM, Simon de Vlieger <simon@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@gmail.com | Brisbane, Australia
participants (3)
-
Nick Coghlan -
Simon de Vlieger -
Stephen J. Turnbull