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- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] #Python3 ! ? (was Python Library Support in 3.x)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In reply to the recent post by Laurens and the vow I made to change the text which is presented on the python-commandments domain I have asked Laurens to write a new text on the subject. This message is a heads up to let all of you know that this new article is now available on the following URL: http://python-commandments.org/python3.html This article will probably be the featured article on #python's /topic regarding Python 2 or 3. I also read some remarks about possibly having an official article up on the Python website and in case that happens that will take the place of this article. Regards, Simon de Vlieger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQIcBAEBAgAGBQJMHoQxAAoJEBBSHP7i+JXfGdUP/3NsUuMAJ2DONJZE4AbQIx5G n7UE/SD0teZpyrYYIzV/PI1m40xz5XBe+zJyNfGN7m+MNoW7lGIxHgBoTB5CU6eE 10LeNy2qR9eqRQ/NZ+t8GJul4zuGIocPglDqCX/M6KtFCmtDsgSgbLaMFEgI4lRs vZr9I9hUX9E1r+9T50uxo/YHQm+QW/HIYVks15nOoeUalkhxlQF67vvzH8/lds/F sl5DxXe/zo287GeOIjpDNI/+0KJtUTLop4S/cpVxxA5eNX9lgGztq1wmKCMQmKcB FS/WfQomyEhZhTk4CtIMQ7HM51bGUHwDeoO8qIOrayTM8ucoruO0QyzmZM0yxoDY G+GVYabTKKp9ICDaUvOMxYpRnuz/Xb10nb9HphutQ03cjR28bJLR8nuLUBmIzcJK ICXVIcV11hD01hzGWBJ7llQeoHl9ykaZu54PqpnZ/gdUrBVJ7VRItb5b4wP/PTwJ frtNvnVwBnuR9wfQmCV9Do1UVTAVUqjFRpoBujIgSaZCa1wyF5U+8eHVD26u8lDj +Hva28S/MggzIbc9x3/yv070204JaZVD1Q6fR5cSWdCMHgEDnwCmRjqlqLRW7zqS al4/JaxDiqa7RrB8+liFDijtqopy7K6a3vDK4BBHuyqWmJ9lGqVJzC0ynRE6DV7N 4+lJCEF9qLW++QgjHXR2 =qRiB -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] #Python3 ! ? (was Python Library Support in 3.x)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20 jun 2010, at 23:53, Nick Coghlan wrote: About the only specific wording tweak I would suggest is that "little regard for backwards compatibility" should be phrased as "less regard for backwards compatibility". There were still quite a few ideas we rejected as gratuitously incompatible, even for Py3k (the eventual decision to retain old-style string formatting comes to mind). I have changed this text to include the wording tweak. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQIcBAEBAgAGBQJMHp7DAAoJEBBSHP7i+JXfSkMQANw1SNroVYNkDUEJCIKtdKEJ HyGBMZpG0liUfqVf8YAjNRYEscpWtsS2Inh8PBlTUwo5OTZPmbggJVZGO17E7Z8k ld9TASppKraNZL62nBno5us2rnc2aUJL6GCaKPL1SQkk8GG1yLAV57j8d4R50QZS 4S7ogFPgVveM4VYEZXaZrlHpzlHjdh8xjq7f4Pl8IKJQZm6uOorK+sL+jiw0DauA UEJ53rx0agy8GRwtnOY7XvqP0lgXLfZ/axTW9e6FkKXBcHYv3qdEAvdC3wyF9OKJ nSNo7vIj4z24V7x9WQdIcc2wifHGPqSBSfnUc4Y3TPAaPLAjlX3HX3C4J+iFbI4/ c6VIm/OSPhcuclV0IgTJGvDOoyVlxTXFnOhOobXFI3KcAtCMQw5Y9gzx+4f5nahJ YMlu54lFhqMsBzsTMlYcispEbbAuban4aZH7JAZ645F/AMzGqiTUZyHgD+A+i+9P Ctu7DStT4tI/ZHcsqjnSkmpLxFhr3kNZct71aS22xOpm4MBAXmPEFYa2a/LpozHi pDhuKJbwNc/+lbgiK267IP+V2pfKQ73qMQhn6hq0IPAgBXNu8fHJ6af6bygmIr/S sK/0zddz3C2qCgqHmYGBwYfrmQB0fgM4ic9Zi2I9/flH+6cLolhSHkOqGkH1m0DQ totdE00iTLVuy6VEmMmm =NcT9 -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] #Python3 ! ? (was Python Library Support in 3.x)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21 jun 2010, at 23:03, Lennart Regebro wrote: On Sun, Jun 20, 2010 at 18:20, Laurens Van Houtven wrote: 2.x or 3.x? http://tinyurl.com/py2or3 Wow. That's almost not an improvement... That link doesn't really help anyone choose at all. Lennart, That part of the topic will be replaced after all feedback is gathered on the new article Laurens provided at: http://python-commandments.org/python3.html as stated earlier in this thread. Regards, Simon de Vlieger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQIcBAEBAgAGBQJMH9j1AAoJEBBSHP7i+JXf8qQP/1w6Esl/x6S5+4lDqykx0R7w M9v6x8G2JvnthTkzh2hF76vruLc4e3SNs1QVCmirh5vjdkRHneJQ/2w/dRVKLi2b /tayYg5QyzjPL37wiAarRnsr7SSiwFgEUCHWZVAAw0dRvszYF/CoLmxTs8TQWs8o KnRuwO4UHuXvtarqO8JeY6gMR4bwcdEXHVNqdRK+PSoRXH9IVJky6IcqwtTC0bzf vyLlQZmVdiXIXvjYOxNQgoufmsC74daqqodzhxtCn2WTHSN2s1ws/gkxBqe+NZPz zYlAukVSiLz/YMcK3NGZYukseT8ZBGiNMuhPVt3lb4SY2LnKVRUiYqNCp9wpWCr/ ASmjaZDU0Dz5I+PHSNCWC4NHyTNClPy3b4b9y3LJ/6hpNZaC3wGHTX5IDxQKjt5u ajEgzstM2wuZDtVNQhcADHk2KWBsCoaE9c0tXKz40T7nIq15zbbGqhyTXjmyouLB JoonSPbS5Ap1UY6RGWEt6t3ZdVDDnMwJzL/DBMOiMgWZIVf7B6/VPy0j9jV9U0WV Sx+U5WnaYqKYo+ZkRTg1iI6dPuK5GTGph+2gzjdTHRVMFFPETxkFz/pBZJG4DOHq bkaKG2IFMWB+Ua9GrTJTbfmTP3YzgJwBG34ZWRLFSQu7zJaY1JdQqQK7z+SCJ5Lg toMEpj7z8KxfUAF84xBG =hTod -END PGP SIGNATURE- ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] http://bugs.python.org/issue231540
On 24 July 2010 01:39, Mark Lawrence wrote: > On 24/07/2010 00:09, Paul Moore wrote: >> >> On 23 July 2010 23:26, Mark Lawrence wrote: >>> >>> Is there any money to pay for the forthcoming 10th birthday party for >>> this >>> issue? Is the OP still alive? >> >> I'm not sure the sarcasm helps much. What do you suggest should be >> done with the request? Nobody has provided a patch, so there's nothing >> to commit. Closing it as "won't fix" seems unreasonable, as I imagine >> that should a suitable patch be supplied, it would be accepted. >> >> There's no magical means by which such a patch would appear, though. >> The OP clearly[1] is either not interested enough or doesn't have the >> skills to provide a patch, and no-one else has stepped up to do so. >> >> Note that it's been classified as a feature request, not a bug. So >> there's nothing wrong, as such, with it remaining unresolved. >> >> Paul. >> >> [1] I say "clearly" - it may be that he could provide a patch if >> asked. Maybe it would be worth you contacting him to ask if the issue >> is still a problem for him, and whether he can assist in resolving it. > > Paul, > > I'm on the verge of giving up my time because the whole system is a complete > and utter waste of my time. I feel quite happy that in my brief tenure I've > closed 46 issues, but there's so many more that could have been closed, but > yet again you don't even get the courtesy of a response when there's more in > the pipeline that could be closed. I'd quote the issue numbers here and > now, but I'm just too flaming tired to do so, though a quick count indicates > I've got 23 ongoing that I'm attempting to sort. > > As it happens, I have been having discussions offline in an attempt to shift > the culture of Python development but I don't believe that anything will > come out of it. Let's face it, development is much more interesting than > bug fixes. And once again, if some stupid idiot volunteer bothers to put in > a patch to the code and/or the unit test, and it sits and rots for five > years, is that person likely to come back to Python? Strangely, some do. > > Sorry, I'm off to bed. > > Yours feeling most disillusioned with python-dev. > > Mark Lawrence. Mark, when I read your emails it seems to me as if you have the greatest concern with improving Python, the language and improving the state of the bug tracker. This is a great thing, people like you are much needed. However, I do seem to notice you try to take a business-like approach here on this mailinglist. Most people on python-dev are volunteers who (like you) spend their free time helping and working on Python. People who work in their free time are less likely to feel obliged to respond immediately to an issue. They are also less likely to keep paying attention to the bugs they were assigned. I think a person like you is needed, someone who weeds through the rotting bug reports (not the feature requests) and tries to follow up on them. Is the issue persistent for the user, has it been fixed as collateral on another fix, etcetera. However, I think you would get more done if you switched from a business philosophy to accepting that most people here are volunteers, don't try to pressure volunteers. Try to do the best *you* can within the community and let that help the project further. Oh, and with business philosophy I mean: mails like the one you start this thread with are interpreted by me as being very pushy, overly sarcastic and if my project manager at the office sends me an email like that I know I have to do it right now. I would dislike to be spoken to like this in an voluntary environment. Do note that I do understand where your feelings come from. Regards, Simon de Vlieger P.S. a feature day sounds like a great idea! ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
