Re: [Python-Dev] Unicode 5.1.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 25, 2008, at 1:53 PM, Fredrik Lundh wrote: Barry Warsaw wrote: I agree. This seriously feels like new, potentially high risk code to be adding this late in the game. The BDFL can always override, but unless someone is really convincing that this is low risk high benefit, I'd vote no for 2.6/3.0. at least two Unicode experts have stated that they don't think the changes are that important. determining exactly what the changes to the *core* character database was the whole point of my offer to tinker with this. You don't mean the experts claimed they weren't important, right? Unimportant changes definitely don't need to go in now wink. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSLMCSHEjvBPtnXfVAQKgLwP/YlrqcdlmoeBsK9JdJMnxkgN92L1K86cg lzvQT6bv8vda64Su8bV81UT+NdoB+/ZGpZ1t+Dn4Z0uvB0uaVrZZ7uOUoqQTkvG7 yrj/Clbedi2v35vYjudqAaZyBnJtz+V0rH8tdgpDVU5zILSK4gQm385nFuoUXQpC iJlqok3tjuU= =YfQR -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] Unicode 5.1.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 25, 2008, at 2:15 PM, M.-A. Lemburg wrote: Guido's request was just for updating the Unicode database with the data from 5.1 - without adding new support for properties or changing the interfaces. See this page for a list of changes to the Unicode database: http://www.unicode.org/Public/UNIDATA/UCD.html The main file used for the unicodedata module is called UnicodeData.txt. That's much less scary. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSLMDCHEjvBPtnXfVAQIrYQQAoABjn/KWd8VdFeplR1i3Lqx5lNAWiJu9 6QWhE/4PPGpCBWhsUejnqHTdCOHmo7y6g3YWwPJ1hDZbl+oXrHd4/bcnHWMJgbOO BV7ACRdVcf9tuewiyNkWXGDn99WcXrGHSTXEnhQsQWL58PDbLxbbDgDUPdbXsGgC zCQbSykYv2E= =yheO -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] Unicode 5.1.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 25, 2008, at 3:17 PM, Fredrik Lundh wrote: Barry Warsaw wrote: You don't mean the experts claimed they weren't important, right? Unimportant changes definitely don't need to go in now wink. Well, at least Guido managed to figure out what I was trying to say ;-) Yeah, I was just being curmudgeonly. :) - -B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSLMJq3EjvBPtnXfVAQKG6QQAl3MliLaqhaibf12INX6EUoeIiYBEJlhY IiFgdc6VXe7evMsxUj2xE+1S+rg9BEhwiY38NTZdaqDCRiHBUY6aKFYlnawuyaKf 8m+jIdkJyudBpT5dBvfBCvYlwmXl/RwKHzDRDCHUjKfBVgAo9elv+EDy2kFLUpM1 W8dVEYwo3dg= =fue6 -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] Mercurial mirrors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 26, 2008, at 12:42 PM, Benjamin Peterson wrote: On Tue, Aug 26, 2008 at 10:53 AM, Antoine Pitrou [EMAIL PROTECTED] wrote: Hello, Thanks to Neil Schemenauer, we now have some Mercurial mirrors hosted at http://code.python.org/hg/ Cool! It's nice to have these become official. My hg branches are all pointing to your site. Can I easily relocate the parent branch? Actually, right now anything that's not Subversion is still experimental. But agreed that it's nice Mercurial and Bazaar are available. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSLQ6yXEjvBPtnXfVAQK/fgP/aRTdNeqdWddQetANArV8zpYLbS7TUUbl b/h0p6fWJdSf4ZPkuN4yjXZz8F+4QXc+B1qF8qxEdtc9BjvSBbgOED/GEjF++9OJ fQ2JpT01+Cj2Z8rl034leTrGq1CQ9uDC7YTWJblJjyFiFiCEzSiiJ6aETe3LDpwe ZJT6OxyQVwU= =7YSu -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] Mercurial mirrors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 26, 2008, at 6:28 PM, Antoine Pitrou wrote: Brett Cannon brett at python.org writes: But can we push branches up to our personal directories on code.python.org like we can with bzr? If you have an ssh access to code.python.org, it should be easy. However, giving other people anonymous read-only access would require some manual configuration I think (not lots of, though). It should not be too hard to adapt the generalizations we made when we brought up the Bazaar repository. Unfortunately, I don't have time to do it, but Thomas and Martin (who are both also probably pretty swamped) probably know how we did it. If not before, we should spend time after the releases in making this available. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSLSS03EjvBPtnXfVAQKAVQP+KCbGOHU0xjfR1mghhdPhlzhHslC1Jwc+ WJAIoDfO/qWGwzBBImIoEqsAqdEBWVbaEjQN57EtL0LRUoR0S3bJdg9P/EeOBDlv 2RHxYZomMFE4rlUJer27oHVBXRO/MgIfWiePQEHowEQQ1pe4INnqiF0OeMlou8sb fYsrpEIun5k= =gtAb -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] 2.6b3 Windows installers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 2, 2008, at 8:09 AM, M.-A. Lemburg wrote: I suppose this is due to Martin building the installers and him not be available at the moment. He should be back today. Since Python on Windows will likely only get very few beta testers without a Windows installer build, I'd suggest to postpone the RC1 release that's planned for tomorrow to get more feedback for the Windows builds. I'd rather still release the rc tomorrow. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSL0we3EjvBPtnXfVAQKbRgQAhNM2q8M4Yd0IhbEd2+DWtZnfALdxXr8e vfK0h3tH3+DZuEYyNLZHQOwLC7uUjqcKXc/y+v0EwY7Q13tYz0TCVcLY+0zbXsoi on0TMh8kn/Wwlw/byKc8K3HFkKU4mhzxmLm4oq/8sbsQPABjkEtgNEXP4enmZFLU U1R8E273MjY= =e7/S -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] 2.6b3 Windows installers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 2, 2008, at 5:58 PM, Benjamin Peterson wrote: On Tue, Sep 2, 2008 at 7:24 AM, Barry Warsaw [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 2, 2008, at 8:09 AM, M.-A. Lemburg wrote: I suppose this is due to Martin building the installers and him not be available at the moment. He should be back today. Since Python on Windows will likely only get very few beta testers without a Windows installer build, I'd suggest to postpone the RC1 release that's planned for tomorrow to get more feedback for the Windows builds. I'd rather still release the rc tomorrow. Even with 41 release blockers, are you still planning a release tomorrow? I guess there's nothing wrong with that; the more testing the better! 2.6 and 3.0 are also pretty stable; we're just ironing out a few of the rough spots. :) I hope to start going through the blockers tonight. We'll see! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSL24SHEjvBPtnXfVAQLQ0wP8D3zjs97No9dnR8WgOV/4IJHGQ4FK0e7k XadqGmdEy0uLlpfjxCuBjWhdq5q1n/NPuJtX/wVtf0CQZtadb8gFde88+KyPkwYk T8eAwz7OFv+kmclj2tnGh1Raps+0ocBrG5BWJG3D85ofGIZL4NZTLkDr9b6LDONA lr85NvbpqMg= =bj/j -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] [Python-3000] bsddb finished for 2.6/3.0 (and class 'BytesWarning': str() on a bytes instance)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 3, 2008, at 7:01 PM, Jesus Cea wrote: Barry Warsaw wrote: and I know Brett agrees, so that's it. On IRC, I've just asked Benjamin to do the honors for 3.0 and Brett will add the deprecations for 2.6. I just committed the fix for bsddb testsuite in Python 3.0 branch: http://www.python.org/dev/buildbot/3.0.stable/changes/2687 Can I do anything to revert this decision?. If not, what can I do to be reconsidered in 3.1?. Start raising some pitchforks. It looks like Raymond will join the march :). Really, this is about what's best for Python and pybsddb. In this article, Guido unambiguously states his opinion: http://mail.python.org/pipermail/python-dev/2008-July/081362.html +1. In my recollection maintaining bsddb has been nothing but trouble right from the start when we were all sitting together at Zope Corp North in a rented office in McLean... We can remove it from 3.0. We can't really remove it from 2.6, but we can certainly start end-of-lifing it in 2.6. Jesus, let me stress that IMO this is not a reflection on your work at all. On the contrary, keeping it alive in 2.x and providing a really solid independent package for 3.0 is critical for its continued relevance to Python programmers. I completely agree with Guido that bsddb (not pybsddb) has been a headache since forever. For example, IIRC Sleepycat was notorious for changing the API in micro releases, though I don't know if that's still the case with the current maintainers. I personally believe that Python and pybsddb are both better off with their own maintenance lifecycles so I stand by my decision that pulling it out of 3.0 is the right thing to do. 3.1 is far enough away that any decision we make in 3.0 can be re-evaluated. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSL85BnEjvBPtnXfVAQLfkwQAtoagOP37uAwL1r2H7w73erTsWBYHf4VH KcTZsjeQ/mEvmaaJIG86ylAtpxmDmMF5x7OClR66bXXxf0oTnWV4KMC9rLdQW8R/ KpMIfuQw/501AQgFmcB0M6SQ6CYyJHU5K+K6X+ScOPHOJoG8usPK1pk8XFGOXBZK UGXCEHVvlrk= =7AOQ -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
[Python-Dev] Not releasing rc1 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm not going to release rc1 tonight. There are too many open release blockers that I don't want to defer, and I'd like the buildbots to churn through the bsddb removal on all platforms. Let me first thank Benjamin, Brett, Mark and Antoine for their help on IRC tonight. Here are the issues I'm not comfortable with deferring: 3640 test_cpickle crash on AMD64 Windows build 874900 threading module can deadlock after fork 3574 compile() cannot decode Latin-1 source encodings 3657 pickle can pickle the wrong function 3187 os.listdir can return byte strings 3660 reference leaks in 3.0 3594 PyTokenizer_FindEncoding() never succeeds 3629 Py30b3 won't compile a regex that compiles with 2.5.2 and 30b2 In addition, Mark reported in IRC that there are some regressions in the logging module. I appreciate any feedback or fixes you can provide on these issues. You might also want to look at the deferred blockers to see if there's anything that really should be blocking rc1. I'd like to try again on Friday and stick to rc2 on the 17th. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSL9Y53EjvBPtnXfVAQJGXwP+JZUa5EWlQh7yzt7aFdEM3qgiFZnKqWhz TN4Cen0/eK8c4+t8a5WC+OLvc/P3PhMPhLSnE+g6IqQUO+pt+2LANgpAvCUrUahc Nk2pt3gCclcmWlzVvCBspVPZjFPkHsW0uVhgK6x1C/2Re90yjeBqPGgT4LGlmaR3 bz6A3iiUnk0= =Y5aN -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] Not releasing rc1 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 4, 2008, at 12:14 AM, Raymond Hettinger wrote: [Barry] I'm not going to release rc1 tonight. Can I go ahead with some bug fixes and doc improvements or should I wait until after Friday? Doc fixes are fine. Please have bug fix patches reviewed by another python-dev member. Bonus points for any bug fix that closes a release blocker! :) - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSL/cL3EjvBPtnXfVAQKnmgQAlx89LWeq0hEmTRvTGy/DHIYioARqAisG wJAnZPqinbGI6pkyn0kiwgDOvNzstnFQSZsEFiAFU+iF+nbgkm8agcTf+eLXqCFK y+o0xXTi7fLXKuaGioY54kz3BcwQH17Ul3X6vRxBdCWYesAe3rIXprnNgt/Euuyy P5sZLKwfTls= =b3n4 -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] [Python-3000] Not releasing rc1 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 4, 2008, at 7:08 AM, [EMAIL PROTECTED] wrote: Barry In addition, Mark reported in IRC that there are some regressions Barry in the logging module. Vinay apparently checked in some changes to the logging module with no review. In the absence of obvious bug fixes there that should probably be reverted. Or did he commit Mark's patch from bug 3772? If so, that would count as a reviewed patch. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSL/cpnEjvBPtnXfVAQIkSwQApjBbIGgyV3X1oBhBLtRjTZrVDgFXPfRH XyXtVd1r75PT+24UuqPHWNC9l+/sKnUaYqH3kJbHG2duMyr/duG7j6EIJLzOz+QC SKwqtQr+WDBR0vpH3Q0wrUzQNXhtDyCjWx84IatRbKRVDUfbDlFQy/jj+SLvRBBR WGJTAFP1x5g= =mebg -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] [Python-3000] Not releasing rc1 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 4, 2008, at 7:31 AM, Facundo Batista wrote: (I'll be hanging around in #python-dev today and tomorrow, btw, ping me if I can help you) Me too, though I'm a bit busy at work. Ping my nick 'barry' if you need any RM-level decision. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSL/c2XEjvBPtnXfVAQJ4EQP/SecaG0VRtsezedDRpX+zwmVo6W0n+9EP rmKH5CWMSTWh53rXySCmE8IS2rrdhoyCZNSy0aERMTGz5JuEh/sw+O5EaxJQMFST DdYx0aLRVwb62JaQHr7W7YyVWBG5+CQa3BehASFiwsw0dsAp0BpkwW1nIhybkLcW hXNRzB2gwXI= =9Mgt -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] Not releasing rc1 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 7, 2008, at 10:51 AM, Fredrik Lundh wrote: Barry Warsaw wrote: I'm not going to release rc1 tonight. There are too many open release blockers that I don't want to defer, and I'd like the buildbots to churn through the bsddb removal on all platforms. I'd like to try again on Friday and stick to rc2 on the 17th. any news on this front? (I have a few minor ET fixes, and possibly a Unicode 5.1 patch, but have had absolutely no time to spend on that. is the window still open?) There are 8 open release blockers, a few of which have patches that need review. So I think we are still not ready to release rc1. But it worries me because I think this is going to push the final release beyond our October 1st goal. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMP6/3EjvBPtnXfVAQIprQQAsWgxQPKyxM/rrG5TWL4UqI7xne6dLTjL Nx3OBpi8hcNXEqyxzoosFXXZy4PpSWU+SwxuI1YQT9rUjv/ks6yxu3cBcEVhtEHV KE34YS4D825tVGvbvpsOXF06fsfv5j5zZGB6hlSipZoiv1rhR3uEsO2zkWaI4eQ6 Ty2Cfuxu10A= =8eP5 -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] Not releasing rc1 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 7, 2008, at 4:12 PM, Fredrik Lundh wrote: Barry Warsaw wrote: (I have a few minor ET fixes, and possibly a Unicode 5.1 patch, but have had absolutely no time to spend on that. is the window still open?) There are 8 open release blockers, a few of which have patches that need review. So I think we are still not ready to release rc1. So what's the new ETA? Should I set aside some time to work on the patches, say, tomorrow, or is it too late? It's not too late. If they fix bugs and the code gets reviewed then yes, you can check them in. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMUlmHEjvBPtnXfVAQJ51QP7BdUGcKN4+L9vD+g7y2TI0+TSw4Ms+eAc yXprcbQnfGp1+uxzjiTCeAv0OSAodw4aakAaI4wzrAkKYNmsVaWOiGKiKrLvR7+Y ++qBxxxVwlKL606hlJCKgphD4hbZcW1w3wY94CXkmrTqyZe/XrStvBj7X10gWeYW lwC3ATaQQ5Y= =tyym -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] Not releasing rc1 tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 8, 2008, at 7:37 AM, A.M. Kuchling wrote: On Sun, Sep 07, 2008 at 12:02:06PM -0400, Barry Warsaw wrote: There are 8 open release blockers, a few of which have patches that need review. So I think we are still not ready to release rc1. But it worries me because I think this is going to push the final release beyond our October 1st goal. Should we try to schedule a bug evening some time this week? Monday, Tuesday and Friday are good for me. I might be around a bit on Wednesday evening. (All times EDT/UTC-4). I'm usually on irc. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMUma3EjvBPtnXfVAQIkEQP9HdcmjL3zRLO5yxBt3JEfxd2l924wFgAa avi5VZMA3YFRCqfmfS/BBtng2qTSbzyL8UO9tWSVdtjLd62g2uLuS1UzcBJ+O8qE I1veedtxxoSvjDOoVYmuYy3dS1ZFTEKvEs0PrE2ukoGzPkRpZTAQ1AeTxSXbuRc9 fZXgOWVYg6k= =PQUF -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
[Python-Dev] Proposed revised schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't think there's any way we're going to make our October 1st goal. We have 8 open release critical bugs, and 18 deferred blockers. We do not have a beta3 Windows installer and I don't have high hopes for rectifying all of these problems in the next day or two. I propose that we push the entire schedule back two weeks. This means that the planned rc2 on 17-September becomes our rc1. The planned final release for 01-October becomes our rc2, and we release the finals on 15-October. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMUnWXEjvBPtnXfVAQIEAQQAnut+CRyBAacC2zzptb5l9cphwke0sEjx THJXHCBUfidaEV7SCtyfkh6i+IpqynvFRsKyOYSWsMojAa5rO/iM6ZJLkUav9c62 IzweJ6Nw3UnOJ/7xksCesDVxDRncFtvu0eRUZWDkOsrNawL+Z21DGKtAuau/pgiY sFnKeyP7NX0= =ZNPm -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] [Python-checkins] r66321 - in python/trunk: Doc/library/warnings.rst Lib/asynchat.py Lib/bsddb/test/test_early_close.py Lib/mimetools.py Lib/test/test___all__.py Lib/test/test_excepti
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 9, 2008, at 6:31 AM, Nick Coghlan wrote: It's also a bug that was introduced by the late API changes made to WarningsRecorder in r66135 (when WarningsRecorder was moved from test.test_support to warnings to make it officially supported for use outside the Python test suite, the API was also changed). Instead of changing the API *again* could we please get the API reverted back to the way it was for the two months prior to r66135 and only change the location from test_support to warnings? (obviously, the use of @contextmanager should still be removed since we don't particularly want warnings to depend on contextlib). As I commented in the bug, if this function is added to warnings I think it will be increasingly used as a way for code to suppress warnings. If that's the behavior we want to allow, then I think making every warning but the last inaccessible is a bug. If that's not a behavior we want to encourage then naming this function 'catch_warnings' and putting it in the warnings module sends the wrong message. Better to stick it in unittest if test_support is unacceptable. Or at least name it something that doesn't scream use me in a way I don't intend!. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMZrfHEjvBPtnXfVAQI6DgP8DyNKZyR846u1Qpgbr4X3wOM1J6EcqSlW 74WGUoU80MDWH5wvagAl7Er90oEh0QhX4ogX8UgF8iLSOC7jwa4CgpZsd9a5V8WB 8M0ia/G457vjGYg8XsaD5Dqvuv6NgMcW/2KJCJK3cuzEafan5C+I6n6lKQMAGOu0 j/9/PtIOKmI= =btg/ -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] [Python-3000] Proposed revised schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 8, 2008, at 1:13 PM, Guido van Rossum wrote: Perhaps it's time to separate the 2.6 and 3.0 release schedules? I don't care if the next version of OSX contains 3.0 or not -- but I do care about it having 2.6. I've talked with my contact at MajorOS Vendor (tm) and, as much as he can say, he would be fine with this. They're having problems getting 3rd party modules to build against 3.0 anyway, but if we can release a very solid 2.6 by the 1-Oct deadline, I would support splitting the releases. I really don't like doing this, but if we can get 2.6 out on time, and 3.0 doesn't lag too far behind, I'm okay with it. We'll have to abbreviate the release schedule though, so everyone should concentrate on fixing the 2.6 showstoppers. I think we need to get 2.6rc1 out this week, followed by 2.6rc2 next Wednesday as planned and 2.6final on 1-October. I've shuffled the tracker to reduce all 3.0-only bugs to deferred blocker, and to increase all 2.6 deferred blockers to release blockers. There are 11 open blocker issues for 2.6: 3629 Python won't compile a regex that compiles with 2.5.2 and 30b2 3640 test_cpickle crash on AMD64 Windows build 3777 long(4.2) now returns an int 3781 warnings.catch_warnings fails gracelessly when recording warnings but... 2876 Write UserDict fixer for 2to3 2350 'exceptions' import fixer 3642 Objects/obmalloc.c:529: warning: comparison is always false due... 3617 Add MS EULA to the list of third-party licenses in the Windows... 3657 pickle can pickle the wrong function 1868 threading.local doesn't free attrs when assigning thread exits 3809 test_logging leaving a 'test.blah' file behind If we can close them by Wednesday or Thursday, and the 2.6 bots stay green, I will cut the 2.6rc1 release this week and the 2.6rc2 and final on schedule. If you're on board with this, please do what you can to resolve these open issues. As always, I'm on irc if you need to discuss anything. Cheers, - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMZ3V3EjvBPtnXfVAQKLbAP6A9b0WBB0H/ONZbKie2TazK/qYLthYnZQ iIpfJ2UboOA7dJ/ueXIsD413oI8GTbUOsUlJOWbSzAfJ6oBuPHrjr4IFRCZhchKG lwViDaK/7aWgIusGFpt6y/SgwJBU531wb7o3Lx/P6rLx5Wh5Nr+tvhngt0WkSMSj WtCsy3mmgmQ= =3HdI -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] [Python-3000] Proposed revised schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 8, 2008, at 7:25 PM, Guido van Rossum wrote: Well, from the number of release blockers it sounds like another 3.0 beta is the right thing. For 2.6 however I believe we're much closer to the finish line -- there aren't all those bytes/str issues to clean up, for example! And apparently the benefit of releasing on schedule is that we will be included in OSX. That's a much bigger deal for 2.6 than for 3.0 (I doubt that Apple would add two versions anyway). The MajorOS Vendor (tm) may be willing to ship a 3.0 beta if it's far enough along, though not as the primary Python version. They clearly want 2.6 for that. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMZ4cXEjvBPtnXfVAQL4ygP/fLILvf3NhvmN3R2T7htGm08xt/bOBYGt +BDrV4rapS4j3jo2Cx+McEdjJZCdq9x7BIaTN+4ITwq02LEY5fmhp6NkhzE1dlnq qdgBq8x/Z4AnsxfydtqYrPhrzLWPpdEZElgll5FB6Dj6XIA7cB8tuds2cE7+OXJI Guom1Y0k6Ao= =u4FB -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] [Python-3000] Proposed revised schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 8, 2008, at 10:07 PM, Raymond Hettinger wrote: [Guido van Rossum] Well, from the number of release blockers it sounds like another 3.0 beta is the right thing. For 2.6 however I believe we're much closer to the finish line -- there aren't all those bytes/str issues to clean up, for example! And apparently the benefit of releasing on schedule is that we will be included in OSX. That's a much bigger deal for 2.6 than for 3.0 (I doubt that Apple would add two versions anyway). With the extra time, it would be worthwhile to add dbm.sqlite to 3.0 to compensate for the loss of bsddb so that shelves won't become useless on Windows builds. That seems risky to me. First, it's a new feature. Second, it will be largely untested code. I would much rather see dbm.sqlite released as a separate package for possible integration into the core for 3.1. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMZ40XEjvBPtnXfVAQK2WQP/e3N2rYD2rbsoynEnXvAjzF8lPoPRFDvl hbjERsbB93uSoBPHaTdjtXnW+InC0W4GC5ogHF9wARbzYTJaxx09WmjihX+PvgsW JhXwLpG3gtyclfqSAF8MWZHc4UnKnyUt5UgYBlZrzT0z7FhWmelUPl8QhS8/2n9L oT3qX8eLabI= =Zu70 -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] [Python-3000] Proposed revised schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 9, 2008, at 3:22 AM, Georg Brandl wrote: Even if I can't contribute very much at the moment, I'm still +1 to that. I doubt Python would get nice publicity if we released a 3.0 but had to tell everyone, but don't really use it yet, it may still contain any number of showstoppers. I completely agree. We should not release anything that's not ready. Assuming that we all agree that 2.6 is much closer to being ready, that gives us two options: delay 2.6 to coincide with 3.0 or split the releases. The latter seems like the wisest choice to meet our goals. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMZ5L3EjvBPtnXfVAQJwSQP/U7FFFI8ao5Xesf6F3QFIUMYFeISrlhof 9ynkQXAskUMelAfayGMSd2nD2+buXA7gyBWplAAEF2rtLhZ3N0+zeh/2HnqcY0b9 EtUM5shAIMlb2948IMoXlxSMplH5auBHMLYFnuPAIH9ERXsGVfyihLnUarAfzmT+ XrWfjrU62TA= =CUR4 -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
[Python-Dev] Updated release schedule for 2.6 and 3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We had a lot of discussion recently about changing the release schedule and splitting Python 2.6 and 3.0. There was general consensus that this was a good idea, in order to hit our October 1 deadline for Python 2.6 final at least. There is only one open blocker for 2.6, issue 3657. Andrew, Fred, Tim and I (via IRC) will be getting together tonight to do some Python hacking, so we should resolve this issue and release 2.6rc1 tonight. We'll have an abbreviated 2.6rc1, and I will release 2.6rc2 next Wednesday the 17th as planned. The final planned release of 2.6 will be Wednesday October 1st. If 3.0 is looking better, I will release 3.0rc1 on Wednesday, otherwise we'll re-evaluate the release schedule for 3.0 as necessary. This means currently the schedule looks like this: Fri 12-Sep 2.6rc1 Wed 17-Sep 2.6rc2, 3.0rc1 Wed 01-Oct 2.6 final, 3.0rc2 Wed 15-Oct 3.0 final I've updated the Python Release Schedule gcal and will update the PEP momentarily. We'll close the tree later tonight (UTC-4). - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMpmfHEjvBPtnXfVAQJUiQP/eTXStyp9M0+Ja7iAFfYcpzfM19j9ddBr ocMC+KTDSgci5/rmFw4KdMhqO9TBk2sXIdCd9GInnuMOKtndCKZ/PXaexnVvSVGb P3CpkkMs/vG1itQIc/EXq6CUhzwuxEv9h8Wo8+zcmL05Cc1IrE5d2OYiO0+KQ8ei lW+j/aNKMWY= =w2oI -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] [Python-3000] Updated release schedule for 2.6 and 3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 12, 2008, at 9:19 AM, Edward K. Ream wrote: On Fri, Sep 12, 2008 at 7:54 AM, Barry Warsaw [EMAIL PROTECTED] wrote: We had a lot of discussion recently about changing the release schedule and splitting Python 2.6 and 3.0. There was general consensus that this was a good idea, in order to hit our October 1 deadline for Python 2.6 final at least. Does it matter to anyone besides the you, the Python developers, whether the schedule slips by two weeks, or two months, for that matter? For Python 3.0? No. I am underwhelmed by 3.0 b3: sax and 2to3 are/were broken. A b4 release for 3.0 (at least) would seem more prudent. We will release no Python before its time. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMpsr3EjvBPtnXfVAQKCUQP/WYfGeubbkWjmwI9mlQ4dMbVjGk15imAJ ArIBs4sH9tbZTE12uNhjNgvXRbN+1QfejNeWOEJEAnPdErPAT0TKAmgA2Rj1MmjP ook5+MbxkgkNnKbz8lozMPduclc7Djf22CYboAqiskK7G6LfD1fsCrIMEVSku/HX dQpXGkG/C4g= =FYgJ -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
[Python-Dev] RELEASED Python 2.6rc1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On behalf of the Python development team and the Python community, I am happy to announce the first release candidate for Python 2.6. This is a release candidate, so while it is not suitable for production environments, we strongly encourage you to download the release and test it on your software. We expect only critical bugs to be fixed between now and the final 2.6 release, still scheduled for October 1st, 2008. There is one more release candidate planned for September 17th. You might notice that unlike earlier releases, we are /not/ releasing Python 3.0rc1 at this time. It was decided that 3.0 still needs time to resolve open issues and that we would not hold up the 2.6 release for this. We feel that Python 2.6 is nearly ready for its final release. If you find things broken or incorrect, please submit bug reports at http://bugs.python.org For more information and downloadable distributions, see the Python 2.6 website: http://www.python.org/download/releases/2.6/ (Note that the Windows installers will be uploaded shortly.) See PEP 361 for release schedule details: http://www.python.org/dev/peps/pep-0361/ Enjoy, - -Barry Barry Warsaw [EMAIL PROTECTED] Python 2.6/3.0 Release Manager (on behalf of the entire python-dev team) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMsXV3EjvBPtnXfVAQJFsgP9GxZYQocbDTd0Z/0yEjpHfZ/FTd8y83jV 5JouO07lB8XtLawnWB9hF8sUrCuBVog5He3mLVUPDmlyn30qvjYWMG2J6zW0yYMX yZdjUyUmta0IMCsXe7YXj369xebh4nWuwG4tDygly4donA7GYPXAlxI48MmyDJxw 1v07LM4Dttw= =Nd3s -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] RELEASED Python 2.6rc1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 17, 2008, at 5:59 AM, Jesus Cea wrote: Barry Warsaw wrote: On behalf of the Python development team and the Python community, I am happy to announce the first release candidate for Python 2.6. In http://www.python.org/download/releases/2.6/ , release date for 2.6rc1 is 20-Aug-2008. That is not right. Fixed, thanks. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSNEKK3EjvBPtnXfVAQKscgP+LXF7eWCvQxdgQ1dREvA7OeSyh60FGvBW SHMv0aHKyZgDZlgpjOB4kttVzYNWB0mm0jHfhuYvJ60CygNVCUCjxgZx8f6SK4B/ IaMjWoFH9e4P616jwknfsvxsmZhqzRF3eyIAz3vl7U9fQWv/jsjtaQl5FcIKuH10 33xxz4TH9hU= =S0s8 -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
[Python-Dev] RELEASED Python 2.6rc2 and 3.0rc1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On behalf of the Python development team and the Python community, I am happy to announce the second and final planned release candidate for Python 2.6, as well as the first release candidate for Python 3.0. These are release candidates, so while they are not suitable for production environments, we strongly encourage you to download and test them on your software. We expect only critical bugs to be fixed between now and the final releases. Currently Python 2.6 is scheduled for October 1st, 2008. Python 3.0 release candidate 2 is planned for October 1st, with the final release planned for October 15, 2008. If you find things broken or incorrect, please submit bug reports at http://bugs.python.org For more information and downloadable distributions, see the Python 2.6 website: http://www.python.org/download/releases/2.6/ and the Python 3.0 web site: http://www.python.org/download/releases/3.0/ See PEP 361 for release schedule details: http://www.python.org/dev/peps/pep-0361/ Enjoy, - -Barry Barry Warsaw [EMAIL PROTECTED] Python 2.6/3.0 Release Manager (on behalf of the entire python-dev team) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSNHpw3EjvBPtnXfVAQLW9wP/RBCaUvhuheIh+BjLLIHQFBQi7D3uVgqi l0+4fhhoKGJvtWklLfSM9I1prcjH/d6tzUu4fIOjX7aM+wZSG++vkfmBoehnhyZW AvU9Lax4mqDwhOJA2QA0WMx0obpYYVHeUl7D1g9kWzbRUkZDX9NZGMWThhEOC1qA UA3bBYbvWiQ= =BFNH -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
[Python-Dev] Python documentation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin points out that in the past, as part of the release process, we've built separate downloadable documentation. Do we still want to do that for Python 2.6 and 3.0, and if so, how do we go about doing that? I have this feeling that building the documentation is much different now than in the past, and I don't really have a good feel for how it's done now. If you think we should release separate downloadable documentation and can help integrate that into the release project, you just might be a Documentation Expert wink. Please let me know if you can help. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSNOLBnEjvBPtnXfVAQIQnAQAm6thEThGufep6hzHxBwAN8MTsLb9jxsu Z8GAtX1bdMNOrJczYpU6by0oXPLR2pupnGV1YrAyQyoqpk+K7W8by5Qtg8+ZZcYH GerkqMVtNYn2zY1HhKigivp2JvlqIidRc5D36XS2EJixhZEPcOQDVm34THNQyRJT QasCQwdSAHI= =MbMY -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] Python documentation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 21, 2008, at 6:03 AM, Georg Brandl wrote: Barry Warsaw schrieb: Martin points out that in the past, as part of the release process, we've built separate downloadable documentation. Do we still want to do that for Python 2.6 and 3.0, and if so, how do we go about doing that? I have this feeling that building the documentation is much different now than in the past, and I don't really have a good feel for how it's done now. If you think we should release separate downloadable documentation and can help integrate that into the release project, you just might be a Documentation Expert wink. Please let me know if you can help. There is almost everything ready for doing this. There is a download page in the HTML docs (that at the moment contains nothing). If you tell me where the downloadable files will be on python.org, I can add them to the download page and you only need to build the docs and put them in that location. I've just added a dist target to the Doc/ Makefile, so a make dist should place all needed files in the Doc/ dist directory, from where you can copy them to the desired location. Benjamin has hacked on the release.py script to build and sign the documentation. I haven't tried it yet but it looks like it does a 'make html' and exports that. Given the above, we should change that to 'make dist' and update the PEP to describe scp'ing them to dinsdale:/ftp/python/doc/X.Y using the templates on this page: http://docs.python.org/download.html I notice that for 2.5, we zip'd and tar-bz2'd them. Do we want to also support tgz? We'll have to hack the release script to build the doc zips. I'll try to test drive this whole process soon. Thanks! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSNYvAXEjvBPtnXfVAQKj/QQApu2YzQLZfpazIb6jPxtWDMnpW99+TrRP miMEwURQmncYWIK1kt9RuBpjszjKKw5x/pP9DEy7Slx+AQq13q1U2Ddi8yQmvWGk Sf3rRxBbgG8QM5H67toB/T6kDtti8C0F0OZZFZpG83nAVZuwtomw7ZYZS2P5Qzq+ eZnW5aANX4g= =HF5j -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] okay to add new test cases to 2.6?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 23, 2008, at 4:00 PM, [EMAIL PROTECTED] wrote: Benjamin Peterson wound up writing a test case for the new C atexit module on the py3k branch. A similar test, though different in detail, makes sense for the Python atexit module on trunk. Is this something I can check in or should I just wait until after 2.6 is released? def test_badargs(self): s = StringIO.StringIO() sys.stdout = sys.stderr = s save_handlers = atexit._exithandlers atexit._exithandlers = [] try: atexit.register(lambda: 1, 0, 0, (x for x in (1,2)), 0, 0) self.assertRaises(TypeError, atexit._run_exitfuncs) finally: sys.stdout = sys.__stdout__ sys.stderr = sys.__stderr__ atexit._exithandlers = save_handlers If you don't increase the redness of the buildbots, I think it's fine. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSNlSHXEjvBPtnXfVAQKQ3gP/XJr97CdjZitwSQxrL28xCuLyPfKmtBVA 2hK2ewQxH9Rxrl0BsFZlnBz2vEygPmPWnduu8VT+sjsrFu/Ua9d1Xo06lQ6/fFck Tp/en0KlAyJ6Pjf/1pWahn4ttwk74YG02LiQgUsfOaIUG+8cMfGfrtyUzwGBoKhW 4RBuwpPjsBo= =7Brm -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] json decoder speedups, any time left for 2.6?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 24, 2008, at 5:47 AM, Nick Coghlan wrote: Bob Ippolito wrote: How much time do I have left to get this into Python 2.6? Zero I'm afraid - with rc1 out, it's release blocker bugs only. Anything which can be deferred to the 2.6.1 release without causing any major harm is definitely out - and while a 2x speedup is very nice, it isn't something to be squeezing in post-rc1. Still, that should make for a nice incremental improvement when 2.6.1 rolls around. I concur. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSNo9PHEjvBPtnXfVAQKJZQP/dGcmjO7P9RKIcYsFAwmDdVlCfn2WiGQt WlNgJiIq5tnq4WSyRQMNeDAWZfheq/vHqlDMU6OunIz5jcv0cVNmKkfcW+pTl9Yc 7Ur6mejeAUYrg2jHkimhMv0wpX/lJ+7CrWD1c+3PK+tQD0GgWfen+/xzCkGqlbc8 ompjNE1WPPs= =Jm8s -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
[Python-Dev] Reminder: Python 2.6 final next Wednesday
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is a reminder that Python 2.6 final is schedule for release next Wednesday, October 1st. Once again, I've gone through the release blocker issues and knocked anything that doesn't specifically affect 2.6 to deferred blocker. This leaves us with 7 open blocking issues. Please spend some time over the next several days reviewing patches, making comments and working toward closing these issues. Email me directly if you have any questions, or ping me on irc. Unfortunately, my 'net connection may be a little bit flakey until Wednesday, but I will do my best to get online and follow up as needed. Please pitch in to help get Python 2.6 released on time! Thanks, - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSN1hJnEjvBPtnXfVAQIQfQQAgYr0tuzJhm3LZX/1SaCwRJcX09UvNH1I CjZHs2TKS22MjF9d3mmBgcEJPl9AwGE+6EF6OiSgrsNRoRtnN0MMT3nQo+deRkan P3jUgMFJMFkA7Uq5MmuNnEnKZXa/bsu/8Om/4wqHqvtDXbUQkZPfyE8BFwBzJJSM Aa6Wp3wieFs= =r4iD -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
[Python-Dev] Python 2.6 final today
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been out of town since Friday, but I don't yet see anything in the 700 billion email messages I'm now catching up on that leads me to think we need to delay the release. Yay! I will be on irc later today and will be trolling through the tracker and buildbots soon. Don't trust email to get an important issue in front of me today, please use irc or submit a showstopper bug against 2.6 if something /must/ be addressed before today's release. I'm going to make a test release at around 1600UTC today, just to see how building the docs and such go. I'm still planning on doing the final final release at about 2200UTC. If you need to coordinate with me (e.g. press releases, Windows builds, etc.) please meeting me on #python-dev on irc.freenode.net. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSONrt3EjvBPtnXfVAQJn7wP9HSieFM7daE5vbvsuJGZtHyC2NFmT5Rsm Fd/ce6CvLzGEkUQ5GQs09TtiZZbIYiObUNkbVQBV8Zbu7A9S3fx7PBpHmPOnIIbr Dfw39pphdKE76yoJmC7OkFTlDbOw6rbuD+JLAzCgcjxx1MqL1Cx08vl2/WEJf3Fl izAVTI2Bwwc= =BCvf -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] Python security team
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 30, 2008, at 7:27 AM, Jan Mate(jek [EMAIL PROTECTED] Jan Mate wrote: Thanks for your answer. I guess the process is the real problem then. - From what i could observe, the connection between vendor-sec and PSRT is not really working as it should. (And then of course you need some kind of upstream flow too, because not everyone reports to PSRT.) Please remember that the proper way to contact the PSRT is via [EMAIL PROTECTED] . FWIW, I am in favor of adding a few trusted people to the team, but only if they're willing to actually get stuff done :). Clearly the current team is too swamped to act effectively, myself included. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOOe3XEjvBPtnXfVAQJ5JgP/dDg+SPLeQ4yBQ/CYxJEh3/Xm2B+2KV5U 9RUjp7W7z2iC/Bz7qwJlui0Z30KaaZ/whMqTuh+5ZYDlrmUDUh9Tl88OyngHOBxy R/SYmluOlYUPdmjUHQYWXf5Bl9JVX9vtZ3LaFKPUo8KJf+dQDFSK3guxnIr5+Jjt oJjX+52vilM= =nJse -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
[Python-Dev] RELEASED Python 2.6 final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On behalf of the Python development team and the Python community, I am happy to announce the release of Python 2.6 final. This is the production-ready version of the latest in the Python 2 series. There are many new features and modules, improvements, bug fixes, and other changes in Python 2.6. Please see the What's new page for details http://docs.python.org/dev/whatsnew/2.6.html as well as PEP 361 http://www.python.org/dev/peps/pep-0361/ While Python 2.6 is backward compatible with earlier versions of Python, 2.6 has many tools and features that will help you migrate to Python 3. Wherever possible, Python 3.0 features have been added without affecting existing code. In other cases, the new features can be enabled through the use of __future__ imports and command line switches. Python 3.0 is currently in release candidate and will be available later this year. Both Python 2 and Python 3 will be supported for the foreseeable future. Source tarballs, Windows installers, and Mac disk images can be downloaded from the Python 2.6 page: http://www.python.org/download/releases/2.6/ (Please note that due to quirks in the earth's time zones, the Windows installers will be available shortly.) Bugs can be reported in the Python bug tracker: http://bugs.python.org Enjoy, - -Barry Barry Warsaw [EMAIL PROTECTED] Python 2.6/3.0 Release Manager (on behalf of the entire python-dev team) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOREJ3EjvBPtnXfVAQLAigP/aEnrdvAqk7wbNQLFbmBonIr2YQbd1vEu TyTr5imYXFWGNfv1/JMeMBjMfwpHi1bgPEDTLEZdhDRNj/G1h4NqqnpfJS0lfIaU 4JBKwnsO80se/RGyupcs5f09UdKxOljhbFKEw46CHDkd9lE+cqy2yhetEwyx3c3+ AVC11sjcO54= =Oxo3 -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] RELEASED Python 2.6 final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 2, 2008, at 12:19 AM, Haoyu Bai wrote: Now almost all the pages on docs.python.org can't be accessed. For example http://docs.python.org/lib/lib.html returns 403 forbidden. Thanks to Georg and Thomas, the docs should all be fixed now. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOS6g3EjvBPtnXfVAQKw5wP+I2L6qPZWp1qDs7qSRdlOE5xSAazhnuzE h7gCUWah0tcewuJC38cE7kNAVkpmp9suBbGgI+FRYTeJJpoO109Io4cF4fRvYd2H NpVfhIOo6VUchNTnsdtP4UzuaIKnkCKgWxMPPjMW9jEZlHPNdOC8stTsxOq1FWFt hlJscML5yQA= =wPLO -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] RELEASED Python 2.6 final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 1, 2008, at 11:46 PM, Barry Warsaw wrote: On behalf of the Python development team and the Python community, I am happy to announce the release of Python 2.6 final. This is the production-ready version of the latest in the Python 2 series. Source tarballs, Windows installers, and Mac disk images can be downloaded from the Python 2.6 page: http://www.python.org/download/releases/2.6/ Due to a minor snafu in our build scripts, the source tgz and tar.bz2 files contained some extra cruft. I have created and uploaded new tarballs but I have /not/ bumped the Python version number since they were made from exactly the same Subversion tag. The new tarballs are identical to the originals except that they don't contain the cruft (.svn files and such). If you have already downloaded the tarballs, you do not need to download the new ones. The new tarballs are about 2MB smaller though. With apologies, - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCUAwUBSOUgjnEjvBPtnXfVAQJ3gQP4mxxW9kaaMlsg7yd1uNcgYa29pitYdF2+ DhFgrCajPZpskc3XlKbPcnPJWT8wtI/EIC5QcPEpAWCHECrTUHzPyGLNeMQz0kFF /ZGCGbef7Mc/JaZvEyF6OATnKhYA5XyUOPdddygx6oar/Y6ZbK2JyLR4pvzh+gtQ SA+u6OPIpQ== =7uu8 -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] for __future__ import planning
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 3, 2008, at 5:26 PM, Benjamin Peterson wrote: So now that we've released 2.6 and are working hard on shepherding 3.0 out the door, it's time to worry about the next set of releases. :) I propose that we dramatically shorten our release cycle for 2.7/3.1 to roughly a year and put a strong focus stabilizing all the new goodies we included in the last release(s). In the 3.x branch, we should continue to solidify the new code and features that were introduced. One 2.7's main objectives should be binding 3.x and 2.x ever closer. There are several things that I would like to see us concentrate on after the 3.0 release. I agree that 3.1 should be primarily a stabilizing release. I suspect that we will find a lot of things that need tweaking only after 3.0 final has been out there for a while. I think 2.7 should continue along the path of convergence toward 3.x. The vision some of us talked about at Pycon was that at some point down the line, maybe there's no difference between python2.9 -3 and python3.3 -2. I would really like to see us adopt a distributed version control system. I want our maintenance branches to always be in a releasable state. I want to be confident enough about the tree to be able to cut a point release at any time. I want to release a new point release from the maint branches once a month. Christian rightly points out that with four active trees, we're going to a pretty big challenge on our hands. How do other large open source projects handle similar situations? - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOajHXEjvBPtnXfVAQJ5qgP+I6k+kHMG2zPTvMIstM2wRmhtAPd7kKz9 S6bXllUBzpxQGMYfqR3Ze5/SVUMEV2HvINPDfg816sGOoxs0fMeori398rU97bkH tOFHOEi/KLKMdgGdjGWWnV+iPEGF6stPMX/6nGQDhM5NMzj81hBgF+7U+UNbS7iM dT2wk3vSZHQ= =q4kW -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] for __future__ import planning
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 3, 2008, at 7:34 PM, Brett Cannon wrote: Wow! I guess release.py is going to get really automated then. =) That or you are going to manage to con more of us to help out (and even cut the release ourselves). release.py is really coming along well. I'm planning to spend some time next time around on updating large parts of the web site automatically. Or maybe Benjamin will when he's RM :) - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOei8XEjvBPtnXfVAQLm+wQAgctR3FuylGaST4Y55JIpo8pPOZ8ouzXW L8wymNAz70neXMI2rVWk/qKyRovkwIgSe2GfKX14Vi85WGOw0MFvo2IkCx9VqUML GdpR2j0ixX512/bBknZ3+Jsz5yUrppXBqFOuMHdSkxg/3YZSWKYUjRAUVk/48ujL zbiVD+VJKUQ= =qjlH -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
[Python-Dev] Proposed Python 3.0 schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, we need to come up with a new release schedule for Python 3.0. My suggestion: 15-Oct-2008 3.0 beta 4 05-Nov-2008 3.0 rc 2 19-Nov-2008 3.0 rc 3 03-Dec-2008 3.0 final Given what still needs to be done, is this a reasonable schedule? Do we need two more betas? - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOqxvnEjvBPtnXfVAQIR5QP/coSi2ltsZSpE2dyUg7Y35QcSk/+4ZbGK zF0AgLaOkGs+DFnxRH9vy9kN3JaEkp1MhEpDjkomE7kNpnJB7bWotTrHI67HD9ma ZDqqmaCc02IeUtLm7HuELvofjCgh+gryKWvRc71ErRHmn/YxMGr1OcEirPpx4nZ9 DeDV0OeUtTE= =RchU -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] Proposed Python 3.0 schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 6, 2008, at 9:48 PM, Raymond Hettinger wrote: [Barry Warsaw] So, we need to come up with a new release schedule for Python 3.0. My suggestion: 15-Oct-2008 3.0 beta 4 05-Nov-2008 3.0 rc 2 19-Nov-2008 3.0 rc 3 03-Dec-2008 3.0 final Given what still needs to be done, is this a reasonable schedule? Do we need two more betas? Yes to both questions. I think that's contradictory :). If we need two betas, then 05-Nov becomes beta 5, 19-Nov is rc 2. If we don't need another rc then we can still do a final release on 03-Dec, otherwise we probably go 2 weeks later. I don't want to go much later than that though because then we get into the holiday season. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOrFs3EjvBPtnXfVAQJceQP/QJN7oLM4nG+iXmgdb0NmKzOzaE3J89sQ UWZnc/hp618QNH4JWC8v2bYApFu+iVg3pcv1Lnmhuql6mOuDhSuKKJVA5jTdR7U2 2enhAEY2DXtmav/29nn2Fy6PYcWJy9pE2xBsbBW8qXc6tYww0iEBsz9SU68jPzPk x5LFC5NqmXo= =Kyr4 -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] [Python-3000] Proposed Python 3.0 schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 7, 2008, at 4:28 PM, Guido van Rossum wrote: On Mon, Oct 6, 2008 at 5:47 PM, Barry Warsaw [EMAIL PROTECTED] wrote: So, we need to come up with a new release schedule for Python 3.0. My suggestion: 15-Oct-2008 3.0 beta 4 05-Nov-2008 3.0 rc 2 19-Nov-2008 3.0 rc 3 03-Dec-2008 3.0 final Given what still needs to be done, is this a reasonable schedule? Do we need two more betas? I know I'm contradicting what I said earlier, but perhaps we should just forget going back to beta and stick to ever-more-perfect release candidates? In other worlds release candidates often contain tons of imperfections (I believe I've seen this both for Java and Windows) and the label release candidate more clearly encourages people to download and play with it, which is what we need at this point! Then the schedule would be something like 15-Oct-2008 3.0 rc 2 05-Nov-2008 3.0 rc 3 19-Nov-2008 3.0 rc 4 03-Dec-2008 3.0 final I'm okay with that too. It does seem odd to go back to beta then release another rc. What's in a name, anyway? wink. And it is good that more people are downloading it now that it's rc. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOvb93EjvBPtnXfVAQJTQAP/cmNdzd/SRymxXvW85EnW2NTHUkh1Auw9 bGlbSC0BF2p9ArgbDLPh/X4uatB3UaqoNeq5LTWHL2f9iCnsI7lFMPuexGr+3t4l Xmld8qN77j4GpU6bXL8uUo3/vlhU4MiG5ETl0kMH30f47srOAAGEGZAqW9jAM92I YSkQPSgBdYo= =+s9t -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] [Python-3000] Proposed Python 3.0 schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 7, 2008, at 5:47 PM, Nick Coghlan wrote: Barry Warsaw wrote: On Oct 6, 2008, at 9:48 PM, Raymond Hettinger wrote: [Barry Warsaw] So, we need to come up with a new release schedule for Python 3.0. My suggestion: 15-Oct-2008 3.0 beta 4 05-Nov-2008 3.0 rc 2 19-Nov-2008 3.0 rc 3 03-Dec-2008 3.0 final Given what still needs to be done, is this a reasonable schedule? Do we need two more betas? Yes to both questions. I think that's contradictory :). If we need two betas, then 05-Nov becomes beta 5, 19-Nov is rc 2. If we don't need another rc then we can still do a final release on 03-Dec, otherwise we probably go 2 weeks later. I don't want to go much later than that though because then we get into the holiday season. Do we need the full two weeks between rc's? Or is it too much of a pain to cut releases 3 weeks in a row? E.g. something like: 15-Oct-2008 3.0 beta 4 05-Nov-2008 3.0 beta 5 19-Nov-2008 3.0 rc 2 26-Nov-2008 3.0 rc 3 (if needed) 03-Dec-2008 3.0 final I won't be able to cut another release between the 15th and 5th, so at least that one should be 2 weeks. If we don't need the additional rc, then we can release early, which would put us just before the US Thanksgiving holiday. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOvcQ3EjvBPtnXfVAQK5mwP9GQfw3zNvGhJWiSkZ2gQ1LNr0rnmfVmpF WcDePkz3e5nsOjtkwiN0rlYHIQE9ySPfvtqqrInBW8y97y79mTjiM4S32XHLyAsd WEWRb0ClcLuZs+JveAb8KF5pO0RlDgX9Dd6puuPr8kGa5aN/rosfsnXra1GrYpj3 JQghQ89JNkE= =+Ymq -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] [Python-3000] Proposed Python 3.0 schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 7, 2008, at 4:28 PM, Guido van Rossum wrote: 15-Oct-2008 3.0 rc 2 05-Nov-2008 3.0 rc 3 19-Nov-2008 3.0 rc 4 03-Dec-2008 3.0 final I've updated PEP 361 and the Google calendar with this schedule, except that the PEP says that rc3 and rc4 are planned if needed. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOvfg3EjvBPtnXfVAQKDfwP/Sz9Ioe1tIrKtvD7JPG2cg2F+wfDJrc+9 vqfh6/eMWiUIOeSKJu6+gye7oXRcHwQXAPivNza3993HesOu0TjudnwXfkAlfsdE m09Rh70AXQQiY7JX46etugRC4BwkuNeBo253cvmfo6hPK0ZhOHZSy3H1LkhvvLA6 Cq56CVqDUgs= =i/Km -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] [Python-3000] Proposed Python 3.0 schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 7, 2008, at 6:01 PM, Barry Warsaw wrote: I won't be able to cut another release between the 15th and 5th, so at least that one should be 2 weeks. If we don't need the additional rc, then we can release early, which would put us just before the US Thanksgiving holiday. Er, /3/ weeks between rc2 and rc3. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSOvf2HEjvBPtnXfVAQJDsQP8DRL2gQDMf1eEvgmmijPtVdbfAypZ1XMY huNzPu91v6dpvrogIP5MJbmJnSnka5yk78JIlkbTU4ZHS0ADsQX+IApU5y/SlO9Y FDtIqb+NFoVRFj5xQaN/EEqO8kNpq3WPmaEQJ4HHeDUIzcrbsPxfCm+vbePgnGzI AwhQqCzmX1I= =aQnH -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] Has python-dev collapsed?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 28, 2008, at 04:17 PM, Guido van Rossum wrote: Yes, that's what it feels like. I hope the pace picks up again and we can release 3.0 final in early December still. I really don't want to carry it over to 2009. Don't worry, it won't. As I mentioned before, I've basically been unable to work on any Python stuff these last two weeks. I'll be back home on Saturday so I can start looking at the 3.0 release blockers when I get back. The schedule still has us releasing Python 3.0 final on 3-Dec, and I'm hopeful we can still meet that date. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkIL0wACgkQ2YZpQepbvXHxOQCdFUA4Q3frOjG2GX1ME0hc6uoZ niwAn3deTj4E9KO+K4dMHWlKhKbjbaga =0Py5 -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] My patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 30, 2008, at 11:08 AM, Victor Stinner wrote: Since some months, I'm trying to improve Python but it's difficult because I'm not allowed to push patches and I have to wait for some reviews and then for someone interrested by my patches. Sometimes I just get a good reaction like nice patch and then nothing. Should I stop sending new patches and work on another project, improve old patches and send an email everydays to the mailing list to get some reaction? Barry doesn't want to release Python 3.0rc2 because of release blocker issues. Guido asked if the mailing list has collapsed. I don't understand: you want help, but some of my patches are waiting since many weeks ago... The problem is not just about me, but about anyone trying to contribute to Python: if it's to hard to contribute, people would just move to another more reactive project. Victor, don't despair! Your contributions are appreciated. Let me remind you though that I've been mostly unavailable for the past two weeks at a work conference. I won't have time to look at anything until Monday at the earliest. That's why I set the 3.0 schedule the way I did. One of the reasons why I'm very keen on us moving to a distributed version control system is to help break the logjam on core developers. True, your code will still not be able to land in the official branch without core developer intervention, but you will be able to share your code, fixes, branches with everyone in a much more live way than patches in a tracker. It will be much easier for others to merge your changes, test them, review them, etc. and it will be much easier for you to track changes in the official trunk as other code lands. In any case, I know it's frustrating not to get good timely feedback, but such is the nature of open source projects. Please be patient and don't worry. I'll look at your patches when I'm back in the real world. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkJlMoACgkQ2YZpQepbvXG0DgCePlFiKrAH/UQkQhLb8Mr7dwtd mmUAoJN2pOJN40fOQ0otMSgeVCt5sqLL =Mnta -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] hg branch gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 31, 2008, at 08:44 AM, Georg Brandl wrote: Brett Cannon schrieb: I just tried to update my 3.0 branch in hg from http://code.python.org/hg/branches/py3k/ and hg is telling me it's a 404. Anyone else having trouble? 404 here too. Since http://code.python.org/ serves the loggerhead Bazaar view, I suppose the problem is that the loggerhead app greedily tries to serve all URLs below code.python.org/. Yet another hint at the evil force-Bazaar-upon-them conspiracy wink. Naw, I think I just f'd up the Apache conf. I'll try to fix that. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkKyLYACgkQ2YZpQepbvXG2pQCgh61b5hA7ECT5mNO+vbmJICYR tRoAoJEa3XGzM06qNepsnhHldzLPF4kG =8JK8 -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] hg branch gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 31, 2008, at 08:58 AM, Barry Warsaw wrote: Naw, I think I just f'd up the Apache conf. I'll try to fix that. And by I'll of course I meant Martin. :) Thanks Martin! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkKy5MACgkQ2YZpQepbvXF8PgCdGou6DzXzBfOhZ4QvtJo3oQY4 QKMAmQECJQhxOxqLU1Og7K9OPVZ3VXvN =BdOC -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] My patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 30, 2008, at 10:22 AM, Eric Smith wrote: Ulrich Eckhardt wrote: On Thursday 30 October 2008, Victor Stinner wrote: One of the reasons why I'm very keen on us moving to a distributed version control system is to help break the logjam on core developers. Yeah, exactly :-) Does anyone already maintain a distributed tree? Mercurial, GIT, anything else? Bazaar. Take a look at the developers' pages on python.org, they mention that a BZR checkout is available. I know that it works (though the initial checkout is glacially slow) but I don't know what official support it has or what is planned with it. I'd like to try it out, but the instructions on http://www.python.org/dev/bazaar/ say to get wget http://code.python.org/snapshots/python-bzr-snapshot.tar.bz2 , which is a 404. Anyone know the actual URL? This is fixed now. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ2eDnEjvBPtnXfVAQJf+gP7BvsB7NtENGqbQR7oGMGjie75MrEn362Y hXcgALWn9UkaiSdcrL+b9DFLY8MYppYUvKEJw92gU9jMzIzgcdH57DGBkudx/PHS hkvPhtGewdSX1QY88CkOYjJ7UYnhrhZWUzN67Yea16QKBwPKQFljsC26toqX+08k J+vZDkAsmwE= =Gy0x -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] My patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 30, 2008, at 11:04 AM, A.M. Kuchling wrote: On Thu, Oct 30, 2008 at 11:04:42AM +, Barry Warsaw wrote: One of the reasons why I'm very keen on us moving to a distributed version control system is to help break the logjam on core developers. True, your code will still not be able to land in the official branch without core developer intervention, but you will be able to share your code, fixes, branches with everyone in a much more live way than patches in a tracker. I don't see how a DVCS will fix anything. The bottleneck is in assessing patches for inclusion in the master tree; not enough people are doing that. We'd just end up with lots of proposed branches waiting to be merged, instead of patches to be applied. I disagree. Dealing with patches is much more painful than dealing with branches. A patch is a dead thing sitting in a tracker. They easily get out of date, are difficult to apply and update, etc. Live branches are much easier to review, update, track changes in the trunk, and share. Yes, it still means we'll have a lot of branches to review, but the overhead of reviewing them and shepherding them to landing will go down. (What a DVCS might enable is making it easier to do larger experiments, like the recent Vmgen work, and publish them in a form that people can download. We could create SVN branches now, but that means people would then have commit access to all of the Python source.) A dvcs means that people can publish their branches in a wide variety of ways. Trusted developers can push their branches to code.python.org. Non-core developers can use one of the free public dvcs branch hosting service. Industrious users can self-publish their branches. Anyone with email can bundle a branch and send it via a smart email package (much different than just-a-patch). This means both large and small experiments are very easy to perform. So are small branches that fix a particular bug or add a small feature. In a good dvcs, branches are very cheap to make and share, regardless of whether you're a core developer or a casual hacker. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ2gLXEjvBPtnXfVAQJlaQQAq8uOlzqCjZbukBOj3Na5CqzUu1xaS4RU 356FpQO2TykQDguNp0dOq40JGJGvypsvDCh89YTT+c32M0KfxftQ/h0cHbC7Vjs5 0pXCdXA+WIAyiCVbql7iBxxvmPB2FfEyhN5TPGdMe2R6c+Cp5zCt4zxL6RAeLZ+F ITJsJt4Suvw= =wK17 -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 3, 2008, at 2:46 AM, Ralf Schmitt wrote: On Mon, Nov 3, 2008 at 1:05 AM, Brett Cannon [EMAIL PROTECTED] wrote: I have started the DVCS PEP which can be seen at http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there beyond the rationale, usage scenarios I plan to use, and what other sections I plan to write. I think you really should not exclude any dvcs based on it's implementation language. I.e. requiring it being written in python for the sake of eating your own dogfood is just a very weak argument. git is certainly missing from your list. Sticking with a dvcs implemented in Python makes the best sense, especially when you consider the plugin architecture. When we selected a new tracker, we didn't make implementation in Python a requirement, but instead a high hurdle. Meaning, if a tracker wasn't written in Python it had to be way better than those written in Python. As for dvcs, I think git would have to show overwhelming advantage over bzr or hg to be considered. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ7emXEjvBPtnXfVAQLbogP/RKxjGVs1STW8ghF/99JeRv8fVhwrHQxw d2WyeuOC4wfU1iicEsbjCgTIKQOKmlnzZ1EO/D9DYc565Vv/+pVGJjSMMCmxS0/V w2MXhGUJp9RKjCZEbUKc6aVszvUIAmQNp1GGWTeEZqzaRm/srSJH3XMsyn4/xMjO qdsl1sQgAj0= =ejCl -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 3, 2008, at 12:58 PM, C. Titus Brown wrote: - Sticking with a dvcs implemented in Python makes the best sense, - especially when you consider the plugin architecture. When we - selected a new tracker, we didn't make implementation in Python a - requirement, but instead a high hurdle. Meaning, if a tracker wasn't - written in Python it had to be way better than those written in Python. I worry about the idea of hacking in any way, shape or form, on the version control system used to maintain the Python source code. I place VCSes at the compiler- or OS-level of the toolchain, because you have the option of fundamentally screwing up the entire project by playing with them. So from that perspective it's better to keep it *out* of Python to remove the temptation to hack :) :) But actually more interesting is whether we want to add plugins that assist Python dev workflow. For example, let's say we wanted to have a 'fixes' command that automatically updated the Roundup tracker with the branch information. I'd personally much rather write 10 lines of Python to add such a plugin than any amount of C or Perl, or whatever else. :) - As for dvcs, I think git would have to show overwhelming advantage - over bzr or hg to be considered. I personally have found git very, very powerful and good, albeit difficult to learn. It is guaranteed to scale (unless Python gets to be significantly bigger and more active than Linux, at any rate) and it has a large, very technically capable, and supported user community already. I think there are reasons why git should be at least strongly considered. Powerful, scalable, active development and user community would certainly apply to the Python-based dvcses. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ9ERHEjvBPtnXfVAQLGEgP/VTjZLo4FJQ3oUGZp5eGHJdvkhOkmJPX+ bKhw09eoR6yuKbcRcPkqjqU9z8T4+gCdrOsiyNE98/Cr14xtAr2tYq2zEj0iFb/L snjVaZuelrlzHV3V6avAs3n8ua+X/rb4tG3r7vc8djH4qeAFw3aMYqYDkodL3BoO /x8NVlfPj7o= =z3TI -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 3, 2008, at 1:13 PM, Ralf Schmitt wrote: I have used mercurial extensively (before having used git) and I think git is great. It gives you much more freedom to work with your source code than mercurial. Ralf, can you describe what you mean in more detail? - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ9EnHEjvBPtnXfVAQLAQgP9HFGmvq3dq60oUryeiVXI2sgWQvUXbYzk 6Nhg796sPyGwzuO8PoLq6CvxNzqvah25KMznjOxx0MpMzhSKEgJPJwxkBLpIYJUy Enz3JrLt+r3do0pNLvgkAz9gENh90QLWt1amVvvt2c8ahua2hGpxPN4Y0YUFbeIf bbxP7bcvD+U= =aPaJ -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] hg branch gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 31, 2008, at 6:28 AM, [EMAIL PROTECTED] wrote: Martin I have now restored the original URL structure, and moved the Martin loggerhead installation to Martin http://code.python.org/loggerhead/ A couple nits. Leaving off the trailing / yields a 404. This should be fixed now via a RedirectPermanent. (No big deal though). More importantly, there seem to be no images, e.g.: http://code.python.org/static/images/ico_folder.gif Looks like it should be http://code.python.org/loggerhead/static/images/ico_folder.gif I think Martin fixed these; at least I don't see this problem any more. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ9ogHEjvBPtnXfVAQKSiAP/Y30HaPDs54GaeB1P+e2CIpQANUlsEm5d ePdfPvSKKXbKGjlYI6jsHdT75oT2q0BVo5DDGN6YcU3oISIIZF6X9AP86LXCqLeI FPU1JEsR+Deds3iALxvd2r306c9gzTFz3j30mjvNUF8HinTheE8lG3j0qCnYSVQI aqClcXudv5s= =Adh8 -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] hg branch gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 3, 2008, at 11:54 AM, Thomas Wouters wrote: FWIW, I put one up this weekend, and it seems to be intact and OK. (bzr+ssh://[EMAIL PROTECTED]/python/2.6/ or http://code.python.org/python/2.6/ ) Excellent, thanks! This is getting mirrored with updates, right? - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ9p2nEjvBPtnXfVAQJoVgP+JLJHK9FRK0xsLtiMSW2BrrnYuCjwhidX yRdNK6oE/hiUKGCjO8G+IptqsDJl5MxFKYZ7RAhK9HjCsjoLW/aQc3zAJuwb+dyX fowpwrBV1pPRTB2IP840ImEATfufb8Mwzo5H8G9k+dx1BTHjY4o5JLQXFREBUNuu jUKSPMOr9NU= =wur0 -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] hg branch gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 3, 2008, at 4:39 PM, Martin v. Löwis wrote: (No big deal though). More importantly, there seem to be no images, e.g.: http://code.python.org/static/images/ico_folder.gif Looks like it should be http://code.python.org/loggerhead/static/images/ico_folder.gif I think Martin fixed these; at least I don't see this problem any more. Right - but only so through a --prefix option to serve-branches. If you make it a reboot-safe service, be sure to copy this option. Will do, thanks. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ9w9HEjvBPtnXfVAQKaFwP/ZnHhz39R52yUFGc9vgJTISFXgTkXk9AS CPeG+FGWuJVdAHHNdIZ7zv8s1Nbl4KoDnHzJdvL2AQjCspJjjibnh/ss39BlGxZe Qq4FFsbKX59NWL0lbBAyKrHRBT2eX1EIbGgrBvGgNUSHRecoJC30UpIxz/DC/cur xdSg7kK/jm8= =cwwj -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] hg branch gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 3, 2008, at 5:22 PM, Thomas Wouters wrote: Exactly the same way 2.5, trunk and 3.0 are, yes. Beauty, thanks. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ98J3EjvBPtnXfVAQLD0AQAhvDoJ85HtO0o/KxeU//kRjid7j0SVIJA OaKnMA/om71Ft5733ZIJYE1jQ1+WFr8TZggiD5NG6d3Af8f8Q0Ep2ujBpOYjKhcQ 85DEmeY2WkoeYqMZXFhEa76BrrPHQtOzEzagRTGIvLnw3W5DbKzTawg8D4z4qmG3 vtQkzEg7Lfw= =cGIL -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 3, 2008, at 4:56 PM, Brett Cannon wrote: But then again, having one scenario that shows svn's weakness directly wouldn't hurt. I could see a scenario where I start to fix something in branch A, realize that a deeper issue needs to be fixed, leading to branch B, and then have branch A depend on branch B. Is that possible? This is something I do all the time with bzr. A related workflow is one where you're developing several inter-related dependent branches. In those scenarios, I personally find Bazaar looms indispensable. I'm told that bzr looms are similar to hg quilt. Until I started using looms I had no idea of their power and transformative effect on my code development. This is one of the problems of coming up with scenarios: you don't know what you're missing. Or is injecting branch dependencies like that not workable? If it doesn't work, then a branch A/B that a branch C is dependent on would also work as a scenario (e.g. reworking the testing framework where you are doing a bunch of different things at once that are culminating in a single new testing branch that collects everything). Those sound like what you are getting after? Let me try to describe a scenario and see if it fits what you're looking for. I'm fixing a bug in urllib2.py when I realize there's a lower-level bug in base64.py. I'd like to cleanly suspend my work on urllib2.py, then push my stack to start working on the fix for base64.py. Half way through that I realize there's also a bug in binascii that I need to fix. I'd now like to push my stack once more to fix the binascii problem. Now that binascii is fixed, I'd like to pop my stack to complete the base64 fix, but without losing all the changes I made to binascii. Similarly, when I've fixed base64, I want to retain those fixes and pop my stack back up to urllib2. I've now got three related fixes. Do I get each reviewed independently or together? Do I land them independently or together? Can my dvcs help me manage all these inter-dependent branches? For bzr, the answer is yes and my own workflow to handle this uses looms, which you can think of as a kind of stacked branches approach. Each layer in the stack is called a thread and I can easily create new threads in the stack. So I might approach the above scenario like so: bzr branch trunk issue1234 cd issue1234 bzr loomify --nick trunk bzr create-thread urllib2-fix # hack hack hack, oops! gotta fix the bug in base64 bzr commit -m'Fixes to urllib2 so far' bzr down-thread bzr create-thread base64-fix # hack hack hack, oops! gotta fix binascii bzr commit -m'Fixes to base64 so far' bzr down-thread bzr create-thread binascii-fix # hack hack hack. ah, all is good bzr commit -m'Fixes to binascii' bzr up-thread # At this point, all my binascii-fix changes are merged in # resolve any conflicts that arose and commit, then finish # hacking on base64 bzr commit -m'Fixes to base64' bzr up-thread # At this point all my binascii-fix and base64-fix changes # are merged in. resolve any conflicts that arose and commit # then finish hacking on urllib2 bzr commit -m'Fixes to urllib2' Here's what's even cooler. Let say, while I was working on all this, someone landed a change to trunk that I want in my branch. I can 'bzr down-thread' to the lowest thread (i.e. trunk), pull in those changes, and then using 'bzr up-thread' merge them into all the threads above. Then I go back to hacking. There are all kinds of scenarios based on this one, and I hope the above makes sense. It's things like this (and 'bzr shelve') which make using a dvcs like Bazaar so nice. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ+BNHEjvBPtnXfVAQLLrwP/aJuetZxYI0S0SvT5QXJG6wARI2K9vdc5 zpUMHofCkxAq4tv/2Ni7g46jUNTayH4A94sAUqjE0QPM3SFl22/TNjga4ZgaHdjt 7Ma9iX7+s5OJenvV0kd3ReN6KvcKQhcQZ+P4DkWBJu0KDxGptUk/WGer3aDdQNzV jn88QaHpEBk= =fPRR -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 3, 2008, at 5:03 PM, Brett Cannon wrote: As I said, one of the scenarios already says patches can be whatever the DVCS supports the best; plain diffs, branches, etc. And the comments for that scenario will point out any perks from that feature. It's actually a profound improvement not to have to deal with traditional patch files as much. The feel... dead somehow, compared to a live branch which can track changes to the trunk, etc. As for the via mail feature, I use Gmail so it doesn't mean anything to me. =) It should though. In Bazaar, a bundle is essentially the revisions in your branch that are packaged to transport over RFC 2821 and 2822. :) That opens up some really cool abilities, such as sending a bundle to a buildbot or patch queue manager for automated testing. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ+CGXEjvBPtnXfVAQKOnAQAs/cr+g091KyjteQaY/quBBIJ53PUoilC MLK9fNLz4jq0eDtl+Rw49rmAFmhKJQaJqx91dZszPEc4FyP9lZByqTbNoCLFhPJP asmxWS263hjx8tXL+RfX+C0Atk9OWzy7j45oa3/J9aBui4ihyI5Yh8/9l8KiCude 6TajzeRcIWs= =6euF -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 3, 2008, at 5:39 PM, Thomas Wouters wrote: Here's a real-life Python example: http://bugs.python.org/issue2292. I actually developed that in two separate branches, one depending on the other: one branch for *just* the changes to functioncalls, to generalize *- and **-unpacking in that context, and one branch to add *- and **- unpacking in other contexts, which was a much more contentious proposal. The division means that the first part can be committed without the second part *without any extra effort from anyone*. I wouldn't have to undo changes, I wouldn't have to reapply diffs or do a painful manual merge were the first branch to be merged into the trunk. It would be completely straightforward and effortless. Great example. The looms scenario I posted earlier would be perfect for this. I do this all the time with larger feature development. I can have 4 or 5 threads in a typical loom, though I know of people who use many more. It makes developing depending features actually manageable. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ+Cm3EjvBPtnXfVAQJkMwQAg3r/JFAOE3RlxbrtPl48QOyjS3PhN7xg +wOoVz+FgLTkx2187xbSqBjy8K69uC3R3Y/1Foc7OmhUEtTGMfmStwoWdjB3f2zi BOgYDPcEaDHC5opfDWtbWpYOJzVcfRJJxhAbevHlKeUSX0/bFd39UY58DXgwR9aI BAjTj4Gt66U= =nbTw -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] XXX do we need a new policy?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 3, 2008, at 6:39 PM, Benjamin Peterson wrote: Grepping through Python's sources tells me that we have over 2,000 XXX comments. The thing that irks me about them is that the have a very slow rate of being resolved, since they usually act more as notes to self rather than easily attainable tasks. So, I propose that we adopt a policy similar to Twisted's: All XXX comments must have an issue in the tracker and an accompanying link with the source code. That way we'll have a forum for discussing the changes and deciding whether they are reasonable enough to implemented. We have a very similar policy here at work. Sadly I don't think it does much on actually resolving the issues. XXX bugs tend to be pretty minor in the scheme of things and they're almost always lower on the priority list than everything else. That being said, we recognize that XXX bugs incur technical debt and reducing that debt is something we're devoting Real Time to doing. I see that Guido is not keen on the idea, and I'm not sure my observations help sway things one way or the other. OTOH, it would be nice if at least we always add our own identifier (initials, nick, email address) and a date to the XXX so we at least know who was talking about what. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSQ+N8HEjvBPtnXfVAQLSPAP/ZKHOTaPxNPySfxPwGmbLSTXjSst+z4/f 1SkhkKjOq8/pjjftZW8n6AWb4WSIWXcyCPJ3FGOAXaP141px2yMfRQnXXbdyH6vQ 6sW12e4ZC2J8UPUyzOxiFJb5F8/HhmIMVifzV1vkEf60QYo9lCD614rBdiW30q9v pWudrLQUMEM= =1USW -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 4, 2008, at 12:21 AM, Stephen J. Turnbull wrote: (2) New repo formats are added frequently, and taking advantage of new features often requires upgrading your repo format. So-called lightweight checkouts can be especially annoying as they involve leaving the history on the server, making distributed work problematic. It should be noted that this is a client-side choice. I can choose to have a heavyweight (i.e. full or partial) local revision history and work in a distributed way, while you choose to do a lightweight checkout and use the repository much as you currently use Subversion. The server side or master repo doesn't care. I like that Bazaar has this option, though I personally don't use it, nor would I teach/introduce it early on, unless I was specifically trying to guide existing Subversion users into the world of dvcs. OTOH, I know people who like this style of working very much. (3) Bazaar is very good at supporting the kind of refactoring that involves lots of file/directory renames and/or splitting/combining. My understanding is that Bazaar tracks changes to directories whereas Mercurial (and git?) do not. According to the Mercurial FAQs I've read, they claim this only affects empty directories. (4) Bazaar is claimed to have especially good merging support. And multiple ones at that. The default almost always DTRT, but what's nice is that if you do see an occasional text conflict, you can usually re-merge with a different algorithm to clear things up. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRBXVnEjvBPtnXfVAQJh3AP+IMnvHQSvuTwQwYCx1zyposZcbF7JBIFc fkbnLBZ1Yn4JDiwPCDthzP2C0h8TAnshjeEPmr+On3sy+DizSxAT73jjhoCY3KoN lqZEaJQ4pGpUg6PNeRjHYxmYQ8vjNhM3gVBXRYjMlEuFG+S5vxhxqcVKvNEjKdl3 vVErzP69D1o= =zcux -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] hg branch gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 4, 2008, at 9:01 AM, Thomas Wouters wrote: Nope, I have no idea how to edit those pages properly, sorry. I'm sure somebarryone does. I do. I've been meaning to update those pages to mention loggerhead too. I'll try to do that today. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRBZ6XEjvBPtnXfVAQKMHQQApaUnvSUFeYu0hI9wFbLm8peQ1miwlrkI KFcZq26nFtQb/rSualxYR1ln82LIlGSLpR9PkYHzpbN+/FYGGXk+IrZ2OsUHalvd 1gsklmeHBc/CdJijFsfUw9XEQUZWgzobeGJz6RH5m4+JY8bmi1AdaNZ2nUnPd56j 50Gq6R0yqUs= =NwuV -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 4, 2008, at 1:00 PM, Stephen J. Turnbull wrote: This is true. Performance is not everything to everyone. Most Bazaar users don't care at all; they say things like who cares about a few seconds in bzr log when it gets the merge right almost every time. But we don't yet know that most Python core developers will feel the same way, and it simply is not appropriate at this point in time to dismiss performance concerns with oh, I'm sure they all can scale. We're Python programmers. We're used to people telling us our tool is too slow. We just say it does the job superbly and it's usually fast enough. :) - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRCQv3EjvBPtnXfVAQK43AQAhexjo3SVeWV9/3PYlR+PQPvZH72XY6XG FuuWN6cfm0XGCAoyRTOv2DfnwYhHw1btYqCeP5yjxOuU1WogOfY1AvpSzWPYDi9R Y1HQArXl9detWSAi5nzL2R8Z57jDnVpLxHscBMGhNxkzyqjQV+Dx2x2Zj3fqw8ac NbOanHZewCk= =4ES6 -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 4, 2008, at 1:21 PM, Cosmin Stejerean wrote: I don't agree with completely dismissing performance just because it's Python. Yes, Python is fast enough most of the time, but when it's not we put a lot of effort into making it faster. That's why we have a good collection of modules with C extensions to speed up computationally intensive applications and half a dozen ways of writing said C extensions. I see no excuse to let the fact that it's Python make it acceptable to have an application with otherwise unacceptable performance. I guess the humor of that got lost in translation. You had to be there. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRCVN3EjvBPtnXfVAQIdOAP/VxEc9ptQdrrJuthZM+wEeYy2eHMTno59 eFGurHysKDl5AUcYPt0dCeP8GAiuvZmU2Vp8/07HmMkgJPPtWbmxHZYTLZ2tEm/A HmXBcsz1icc0dteu0SyeBUwDOz4puv9I5oF6NM879QEt4ykQz0hzM3dVyW6JsfN7 qIlGI8wGEgI= =yUNI -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 5, 2008, at 6:09 AM, Paul Moore wrote: I'll freely admit a (not very) hidden bias here - the slowness of an initial clone (or going through the download a shared repo, unpack it, create a branch and update rigmarole) makes this a nasty test for Bazaar. But I do nevertheless think it's an important use case, as it's all about encouraging casual users to contribute. One thing that we're not taking advantage of on code.python.org for Bazaar is stacked branches. This is basically an indirection technique that doesn't require a full revision history download to get started. Stacked branches greatly improve performance for the initial pull and push, and reduces disk usage on the server. When the new machine is in place, I'll make sure we provide stacked branches for the MvL Experiment. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRGqGHEjvBPtnXfVAQLuSAQAjStZk2nzSsvQN+bDwHryJUVKuutfz9uw ffCjaG9SRiXGaYSfNWs4Ao94fnYiRZVmqYiSHg8NTydR4g54sAF5FKbA1Bgswp9F l52ObdFWKhjwkpfuq1i+IAG2HEqZyiV0naZi4xQmMBKhFd2SFw+qUS9qzGExdCXw PFDYAiS9xKg= =bUlo -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 5, 2008, at 2:15 PM, Martin v. Löwis wrote: Without a doubt the bazaar branches need a little more loving attention to make them a full working demo, but it's mostly details. The branches *do* contain the whole history, and not just 'select revisions': But there are dozens of branches which aren't represented, plus all the tags (IIUC). Those would need to get converted also, don't you agree? Yes. My understanding, though I haven't tried it yet, is that newer versions of the bzr-svn plugin do a good job at a full conversion. Basically, every svn branch becomes a bzr branch and all svn tags are converted to bzr tags, which are not separate branches, but actual symbolic names for revisions in other branches. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRH2P3EjvBPtnXfVAQK/UAP+IuE4hOuixfS/YMv/7/8LYIABIkSxX7BT eO/9295aSeKnY57h32IGyBqPnd67fKYaJ58Be8fDdC3P15ks00wCFIsS4Q2v0LKI pDAxAn5GDRKQFoPZUnpMQXvBwEE9S08jEM7a24cyX111JHX0kVmcFy6nzDATQAv/ g8n03TgS1/g= =AC1n -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 5, 2008, at 2:44 PM, Martin v. Löwis wrote: Yes. My understanding, though I haven't tried it yet, is that newer versions of the bzr-svn plugin do a good job at a full conversion. Basically, every svn branch becomes a bzr branch and all svn tags are converted to bzr tags, which are not separate branches, but actual symbolic names for revisions in other branches. Unless somebody had committed to the tag - right? That would be insane, right? :) - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRH5o3EjvBPtnXfVAQLsYwQAoFSPuMOblPNegZNH63Oz8SrDEG9QMLqO ATvH/HHJAwuQ7Qz4WFiPLJbxf/JWLZZBKM2Idfk5z6icRXr1ynWbPn2SkcTtcAZ6 0G4KCYH/luOPJWTuzuWU+DBLp372Sp3psj2nJXnmmNgaxZyBZospe16pJS+mhpds cIUc6VEGGCI= =cMwI -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 5, 2008, at 8:36 PM, Stephen J. Turnbull wrote: I disagree. This doesn't scale to Python size. For distributed VC to work, somebody has to maintain a repo 24x7. Python has to do this for the trunk; the additional burden for contributed patches is not great. There is no real advantage to having contributors do so, too.[3] Integrators and interested third parties also must keep track of contributor's repo URLs. (Cf. Skip's question about discovering repos.) Not happy stuff. There's an interesting automation available when hosting branches on Launchpad and using a patch queue manager (PQM in particular). I believe this is not quite deployed so I might be speaking out of class, and it's unlikely that Python would do anything but self-host its branches (though this doesn't necessarily prevent the following). Still I will describe this so you see the possibilities. Launchpad has something call merge proposals. When a branch is ready, the original developer creates a merge proposal which is basically a request for review. The dev can ask for a specific reviewer (e.g. barry for the email package), or he can ask anyone on the team for a review. LP doesn't impose a specific workflow, so some projects require 2 or more reviews for any piece of code, others maybe 1 review, etc. Let's say I review Stephen's branch to fix a bug in the email package. I request some changes, Stephen makes them, and now the branch looks great. I can approve the branch and now neither Stephen nor I need to do anything in order to get that branch pushed to the mainline. This works under the covers as follows: when approved, the branch details get added to a queue managed by Launchpad. Python.org would run a PQM that watches this queue. Python's PQM just picks branches off the top, one by one, and it tries to land them. If any conflicts arise or tests fail, the branch doesn't merge. Otherwise, it lands and all the appropriate metadata about the branch (and its associated bug) gets updated automatically. This is a nice model for several reasons. It's the bot's responsibility to do the grunt work of merging, landing, and pushing new branches to the mainline. Humans only care about developing the code and reviewing the results. Also, this aligns with something I've been very interested in from a release manager's POV: I'd like the mainline branches to always be in a releasable state. We can now define that releasable state to be whatever adheres to the bot's landing rules. I'm skeptical Python would ever adopt this workflow, if only because there is technical work that would have to be done (i.e. we'd have to run the bot). Still, I wanted to explain this so that you could get a sense of what's possible. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRMNjnEjvBPtnXfVAQJHXwP/T6WbEIvWC8OJh8i4UnmHvgj8hbT5tbED 2sQRBHNxrBavwhvENUTAM0n4a8j+jSwof8PszflRbiNLVANYKJ1wWHfevkkPcwL7 mzcgtZqpkijWdJoGOeif04LcjuiYopSSEtPLRC9QdDygwlZmhhvbPFVQ2xvtc6C/ 4DO12JDPICA= =Zn9N -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 5, 2008, at 8:36 PM, Stephen J. Turnbull wrote: You need not feel that way. It's not you---the flexibility of dVCS means that until the Powers That Be promulgate a Workflow, this will be ambiguous. You're absolutely right. Adopting a dvcs opens up a much larger world of possible workflows and best practices, both for an individual and for a project. It's a case of too much choice, so I feel strongly that Python should adopt and explain exactly one preferred workflow that will work for most people and use cases. People can still experiment and find alternatives if they want. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRMRb3EjvBPtnXfVAQJU0AQAugEbLciCd2EIzqPrPOmWykoK7+u1fCAh yLnc3aFeserk50WwYkfovZDZESNs8F8ADZ2CIVGK+5AWW+MC17YAx2P4M0gUEeLY ulTQmrpLuRZHVpD6vqoM9hnI/vvsLwTqcYgqB1lfSLdSZ8RnJTnUPQ7UY7Eq7kfS gmxDhUqYKVg= =T9CJ -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] Looking for VCS usage scenarios
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 6, 2008, at 6:35 AM, Nick Coghlan wrote: If it isn't already there, suspending work on something to work on something else would make a very nice scenario to cover, as it is something even the core devs sometimes have to deal with. Indeed. as a release manager, I have to manage several branches in parallel. Several are for patches I'm looking at for release blockers, one perhaps for the PEP 101 administrivia, perhaps another pristine one as a baseline, not to mention several I'd have for my own bugs and features. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRMWtnEjvBPtnXfVAQK1iwP+NShDlAWqvgTh9vO5XbCOSCsC4DXy2KGm eMpG6dBAdbSy4skV0fR9FW1x5b/HrQU2M8y/9LTq4G67DQdkCTzKbJHgW8QaNtG1 BeAhUOaf2URzLlSezbBhrkFxWL45r3bx175eTsKvMhwpxzjSTxCLseT/eaROYlAW P8btKM8Q9xI= =Mrl4 -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] DVCS PEP update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 6, 2008, at 5:43 PM, Brett Cannon wrote: On Thu, Nov 6, 2008 at 06:23, Christian Heimes [EMAIL PROTECTED] wrote: Brett Cannon wrote: I have emailed some people who have shown allegiance to a specific DVCS to seeif they are willing to fill in the usage scenarios for me along with converting the dev FAQ so that we all have a clear way to learn how to use the things. If any of the people I emailed turn down being the leader fo ra specific DVCS I will email here looking for volunteers. Hey Brett! I'm missing a few points in your use case list: * Does the DVCS handle merges over file reneames, directory renames and file moves to another directory? I consider that a perk feature. OTOH, the lack of this is one of the things that piss me of most about subversion. It's really nice when you're in charge of your tool rather than the other way 'round! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRN1PHEjvBPtnXfVAQKULQP9GDRrT76LCZpVRFNCOP6K6CvVGIvtd9I7 ryPk1RFYTqIduEC3FLvhQh0xjxT2HGo/99m0EZZbM4ZxMbhwvM4Sw8ppkcCFwtig aOcHviDr0SNK6DU3L36/zMPN/Wnap3ltF09nqWYcjcbBdR94oae1K7SF7nkPCSn/ oIb2a9ShBAE= =WnB/ -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
[Python-Dev] RELEASED Python 3.0rc2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On behalf of the Python development team and the Python community, I am happy to announce the second release candidate for Python 3.0. This is a release candidate, so while it is not suitable for production environments, we strongly encourage you to download and test this release on your software. We expect only critical bugs to be fixed between now and the final release, currently planned for 03- Dec-2008. If you find things broken or incorrect, please submit bug reports at http://bugs.python.org For more information and downloadable distributions, see the Python 3.0 website: http://www.python.org/download/releases/3.0/ See PEP 361 for release schedule details: http://www.python.org/dev/peps/pep-0361/ Enjoy, - -Barry Barry Warsaw [EMAIL PROTECTED] Python 2.6/3.0 Release Manager (on behalf of the entire python-dev team) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRO7wHEjvBPtnXfVAQIYrQP+Lynpa/p7VMY/YxJyjxiBI0bvOATPIKbE jqu9ZFwXlO19+G4bFiAoYviY5UFYPm3TpbMoso2qNoJsJFLSt4d+AycWWcaXKd08 vpifsxVoWvdLCLZtT7ioMBJh/juu+Pchf2o2l+PHm5aWlLvq/24uu8YKbpSKKbr9 K4gB4ecYd3A= =3UPl -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] [Python-3000] RELEASED Python 3.0rc2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 7, 2008, at 4:53 AM, Victor Stinner wrote: Hi, Great job Barry and all contributors who fixed the last bugs ;-) Thanks! The document What's new in Python 3.0 in should be updated: http://docs.python.org/dev/3.0/whatsnew/3.0.html Issue 2306, assigned to Guido. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRRDT3EjvBPtnXfVAQJUsAP/S9rFA0V4HDp80oxycy0coWDaW2HAnHA4 ombn/+HjWtS2zTIbCkqdFfFsZ05DRDQN7LNKZVkV1sRsmzJ9fASITQP6mpUiFy/f Aq6I0Z73jHlZtINuDRI5ZaCQCrxHPM/lTdjEP3h0fGxtW0wEibr1/rep3gAJMomL 2V6y2mCOc8I= =H0+/ -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] [Python-3000] RELEASED Python 3.0rc2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 7, 2008, at 12:39 PM, Benjamin Peterson wrote: On Fri, Nov 7, 2008 at 3:53 AM, Victor Stinner [EMAIL PROTECTED] wrote: Hi, Great job Barry and all contributors who fixed the last bugs ;-) Which reminds me that this release's star developer award goes to Victor for his hard work on fixing up the networking libraries for Py3k! Indeed, great work Victor! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRSkCnEjvBPtnXfVAQK7MAP/ayV9U241Xi1+s02LNphTwSNhJFDW9mbP UhN1PVINDkS6kqs8GYQ6iO5KsTi20eQxjuTsITLZzFsNuGUKXRcIzkzibWZBMR7m 3WjHC5heGwaxYmaPYmcHUFipdW8T0vYGwiNmk/TWinHx11KSCEhHHeP/Mcr/xd+9 j+VCcl+45pI= =S+vx -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] Released fixes for CVE-2008-2315 for Python 2.4?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 8, 2008, at 7:24 AM, Martin v. Löwis wrote: Skip Montanaro and others hackers started to port the multiprocessing module to Python 2.4 and 2.5. http://code.google.com/p/python-multiprocessing/ Is it planned to include it in 2.4.6 and/or 2.5.3? Neither. For 2.4.x, we only accept security fixes; for 2.5.3, only bug fixes (and after that, only security fixes). New features are rejected. I completely agree. If only there was an independent repository of add-on packages for Python available... wink. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRWJoHEjvBPtnXfVAQIa7wP9FF0+VbZcZWX33RPh8CTVsP/DjVhIvkLr qLIBwyqByyVhx3kNSxHqzPmtSclOjjtfps04rcD7kPi3f9EaOb7vlvlPtiNjU95n ti3nBszrJKLeDzBz3CagpCLVBZbXDGWAD8k3dtMGHuwR6TJZNbrHkQ1PvAaBL/wJ Krw0ph/Qs/8= =Fxa0 -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] Released fixes for CVE-2008-2315 for Python 2.4?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 8, 2008, at 8:41 AM, Jesse Noller wrote: The backported version of MP is on pypi. Fancy that. SHHH! Don't tell Guido you've made dups of his time machine keys. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRXXenEjvBPtnXfVAQIMIgP+MK8WNirYeRiJELSAx7CO++IbqEYjIp7Z +HLvjrKW9X8+Pzl7YuXizeRuUI1fnb5DLYmbB2AfnJs6wPPnTmVv6CJNHFF7g9nU nBCRboHPPihJK4r3tpIRyFqPhitN/Whx7s7brG5YO3tl+JPceMF9oF9X4jMUtr+i hspEMOG5/RU= =rgCy -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] Optimize Python long integers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 11, 2008, at 6:14 PM, Martin v. Löwis wrote: There are some very interesting propositions (with patches!) to optimize Python int and long types (especially the long integers). Just trying to clarify the focus: would you like to see any of these applied to 2.6? No! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRoa1nEjvBPtnXfVAQKwwgP/YvkcFbFc+RDV3VSJ6EHWuBVOdG9YFEGq Riq2GAst7kBMrteMfMHSv0Vb3elngLPRCKxTndUIV9B/ksfVQEHNbz9l1z7HRxmZ 0jVeYCkXCj923bsZ48Gq1MmcZ1d07TERfSVCDXnKooQgj8GlNqT70ru/0+eMFk8d wKLL6cpdak0= =cNoh -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] Optimize Python long integers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 11, 2008, at 6:56 PM, Victor Stinner wrote: Le Wednesday 12 November 2008 00:14:40, vous avez écrit : There are some very interesting propositions (with patches!) to optimize Python int and long types (especially the long integers). Just trying to clarify the focus: would you like to see any of these applied to 2.6? All optimisations patches are long and may introduce new regressions. It's better to wait for 2.7/3.1. But it would be nice to get numbits() method (or property?) in Python 3.0(.1) and/or Python 2.6.1. Anyone remember the bool debacle? - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRodJHEjvBPtnXfVAQK0VwP/f2vyfahYxhRh/ug+ekMp63rhVvy2iMTn VXndnaKqJtJovjuM3YAGQk9/8l6tD4w0DklAi4e175aBvwzRkWb4RwMHGMO2/jn1 mNjloHqku6qIg6+p7jS5ytwsH6sGndgAjARY7jFE8OgYoYPrxtTabgXpr9HM631K a2j8FUmCVQ8= =yirj -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] My patches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 13, 2008, at 9:01 AM, anatoly techtonik wrote: On Thu, Oct 30, 2008 at 4:22 PM, Eric Smith [EMAIL PROTECTED] wrote: Bazaar. Take a look at the developers' pages on python.org, they mention that a BZR checkout is available. I know that it works (though the initial checkout is glacially slow) but I don't know what official support it has or what is planned with it. I'd like to try it out, but the instructions on http://www.python.org/dev/bazaar/ say to get wget http://code.python.org/snapshots/python-bzr-snapshot.tar.bz2, which is a 404. Anyone know the actual URL? Sorry if it is too late. Launchpad has Bazaar mirror of Python code. https://code.launchpad.net/~python-dev/python/trunk perhaps instructions on http://www.python.org/dev/bazaar/ could be updated to reflect that fact. I've updated that page to point to the launchpad mirrors. Thanks. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRxFPnEjvBPtnXfVAQJtWwP/SONN5FuLamUjYtU7s0KIAZ0I3v9YYm0E 4JGLARI+Jugh+IdMlUmJUquA5CZj4FoPgYNl1oK0FPho1IbDzZVQzGu5mjwOPesY nRnzEpO1+lHQlsqTX2NPDYFfgE5DHWvVVWlvbLchazCZNeGD8jIv9708wavEvtZ5 gyuNTLab78M= =chHn -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
[Python-Dev] 2.6.1 and 3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin suggests, and I agree, that we should release Python 3.0 final and 2.6.1 at the same time. Makes sense to me. That would mean that Python 2.6.1 should be ready on 03-Dec (well, if Python 3.0 is ready then!). I'm still planning the last Python 3.0 release candidate for this Wednesday. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSSIgu3EjvBPtnXfVAQKzGgP/XH2szIZdG9nvZTI2M9iWXuz/tBwH6ncd Kv70ATpttQEg/bmuRp5nSmg1p7hxSmTqu9waq4qdc07IPa+ofTngbunUKkTrbZoo E/r72dGw29pou7B6NVh/g5Db8Tl0yNJBd6vmpEUbCvUDBpljqgxCdj0uw/RiDluj 5Ek2biim7ww= =twyi -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] [Python-3000] 2.6.1 and 3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 18, 2008, at 5:03 AM, Facundo Batista wrote: 2008/11/17 Barry Warsaw [EMAIL PROTECTED]: Martin suggests, and I agree, that we should release Python 3.0 final and 2.6.1 at the same time. Makes sense to me. That would mean that Python 2.6.1 should be ready on 03-Dec (well, if Python 3.0 is ready then!). 2.6.1 only two months after 2.6? Why so quickly? Actually, I've wanted to do timed releases, though I think monthly is unrealistic. Maybe every two months is about the right time frame. Timed releases are nice because everybody then knows when a patch is due, from developers to downstream consumers. Anyway, I don't see any added value in the synchronization, so taking in consideration all the effort you're putting in these releases, I would just want to minimize your workload... which is easier to you? doing both at the same time or not? We're getting releases down to a science now! :) Actually the most painful part is updating the web site, so I plan adding some automation around that process too. OTOH, this is the first point release I'll be doing with the new script, so it'll be interesting to debug that process. As for synchronization, I think it's a good habit to get into, if my plan to do timed releases works out. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSSLShXEjvBPtnXfVAQL90QP/UfWRXr0esTim+DtQJs9Fd/+Lj9PpuBV6 UCB7pAwl8uf7qIAwjDkCsdg3VD/wxzmzuwDAB8T19PF5dNxsrKWdBEzhymVpLU8T cch0Vlaevm6Co/kDp8VhyoKlPs7LDhGkC2G04qDSOETo8Ci84rBOlWd7n1KvUrYZ 01Pn6eZHdqA= =k9FS -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] [Python-3000] 2.6.1 and 3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 18, 2008, at 8:07 AM, Christian Heimes wrote: Barry Warsaw wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin suggests, and I agree, that we should release Python 3.0 final and 2.6.1 at the same time. Makes sense to me. That would mean that Python 2.6.1 should be ready on 03-Dec (well, if Python 3.0 is ready then!). Should we release 2.6.1rc1, too? Do we need rc's for point releases? - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSSLSyHEjvBPtnXfVAQJuMAP/cv59kjeFz5DxMk1hMrwXdNQvSs5Ge0lZ ICC4DeKmz0gXZ0+PoZc4Yi9HBAQ8g7ZfKptzIPnEUrg65wV8KS6OzcK5KX5aptvF Mqi+cmD3TPImsOEGoPnJUtlUZ7ZETrY2LSzdIIFqIE5yO1HBt3ohBcdM95+V2zQl zt0uV+F4fnw= =7N3R -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] bytearray methods returning self...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 18, 2008, at 4:14 PM, Guido van Rossum wrote: Good catch, this is a bug IMO and we should fix it in 2.6.1 and 3.0rc3. Ah, a /real/ test of the time machine! Though you can avoid the risk of a rip in the time-space continuum by trying to get the fix into 3.0rc4, planned for release tomorrow. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSSM1b3EjvBPtnXfVAQLrtQP+OEDfWftaUJjLqdKlbH9uSfXKueKUrbJT EZ3HPwSO1Ka5p1zKqNeSiON8MQLTMIzKW2at7YXk4nj0I7YOuho7QxatOVodZ+Er 0bA2w+pnhbJAAcRmhA0nskhXP4F7B8nOJiI6sYpiXxthBYgUu+jsGhad6kky6kwz Kf7PjLIEi3k= =NGqq -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] 2.6.1 and 3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 18, 2008, at 9:52 AM, Christian Heimes wrote: Barry Warsaw wrote: Actually, I've wanted to do timed releases, though I think monthly is unrealistic. Maybe every two months is about the right time frame. Timed releases are nice because everybody then knows when a patch is due, from developers to downstream consumers. From my point of view bi-monthly release are too much. For a ?.?.1 release two months are fine because several issues are found by 3rd party authors. But after that a release every quarter is sufficient. * .1 release two months after the .0 release * .2, .3, .4 and .5 release every quarter * about here the next minor release gets out * .6 and further releases after 6 months when necessary Timed releases have a lot of advantages, and I would like to see if we can adopt them and realize these benefits. What I like most about them is that everyone knows what's happening when and can coordinate efforts. Developers will know automatically (no reminders or alarms) when the next release is happening, so they can schedule what they want to do more easily. Release experts can block out the appropriate time on their schedules and plan more efficiently. Downstream consumers have a better idea of when updates are available and can lobby for certain critical bugs to be fixed in a timely and predictable manner. I think 6 months is too long between releases -- it might as well not be timed. It sounds like the Windows side is a bit of a pain, and since we're all busy, one month is probably too soon. That's why I proposed bi-monthly. I really want our releases to be predictable. I don't think we have to worry about nothing getting committed to the trees in 2 months time. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSSQspHEjvBPtnXfVAQIfwwP8DzaIge8b1rL9/zACiwZ5nOn9S5d+ng+p zjSSvDKgfxX5kEMfUQQuJgI6GIOPvUm0wsmdZnH5f5AD86/1Qz1ugsBkHXO6BWWl LEI2jNjsIU9m1icQkQSnENxJoI5BFFA9upewT1zwo9md4cErzQLiK+WQrblu1hXE GKaxW0Xrva4= =ZI9e -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] [Python-3000] 2.6.1 and 3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 18, 2008, at 5:17 PM, Martin v. Löwis wrote: From my point of view bi-monthly release are too much. For a ?.?.1 release two months are fine because several issues are found by 3rd party authors. But after that a release every quarter is sufficient. * .1 release two months after the .0 release * .2, .3, .4 and .5 release every quarter * about here the next minor release gets out * .6 and further releases after 6 months when necessary In the past, we had been striving for releases every 6 month. This was already very difficult to achieve. While I'm happy that Barry has automated his part to a high degree, my part is, unfortunately, much less automated. I could personally automate the build process a bit more, but part of it is also testing of the installers, which is manual. Martin, I'm keen on figuring out a way to reduce your workload, and also to coordinate releases better between us. I /think/ with timed releases I can tag a little early and give you something to work on so that the actual release is a matter of fiddling web pages and sending an announcement. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSSQwbnEjvBPtnXfVAQIOuAP/fxzFpp886TordGNdd4tusqasL/VK2lpr wbhcfwh5TQbVhkhi9CVUFa7BNXCpgxG1nqWT9+ynSdNKIYKnK8kkjRE7FhEYantP TYkuRGI+2DznKjRBtVNXJq+JNktARWKhQwFkc0AmqooCYvhxqt9T5AkEgN4jRn4s YBLaex4g3rA= =Oi0b -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] [Python-3000] 2.6.1 and 3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 19, 2008, at 2:18 PM, Martin v. Löwis wrote: Martin, I'm keen on figuring out a way to reduce your workload, and also to coordinate releases better between us. I /think/ with timed releases I can tag a little early and give you something to work on so that the actual release is a matter of fiddling web pages and sending an announcement. Again - the work load is not so much an issue at the moment, and I expect it to be reduced even after 3.0 is finally released and 2.5 retired. I would indeed appreciate tighter coordination. Anthony's process differed from yours primarily in him waiting for the release announcements until the binaries are actually available. That might mean that a day or two might pass, but it did help to remove the feeling of working under tight deadlines. Let's try this for 3.0rc4 then. I think all it means is that I won't push the new pages or make the announcement until you verify that the Windows builds are ready and available. We can still use python- committers to coordinate when that will happen, and I'll still do all the release mechanics from my end as normal. It's okay if the announcement happens Friday or over the weekend. I will also try to get up early to do the release before my work day starts, to better coordinate with Euro time. So expect me on #python- dev tomorrow (my morning). Will that work for you? - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSSRrAnEjvBPtnXfVAQJiDwP/ZcbHnwkvWligaP2a3OXEmZ30GZoG1NQn +Lj/j4YNANkhxZ4Vgg9gkMH3mQ+eTwWdqr1/VM3LTW+fFXhdtAaAG1NsvHAlkAE0 N+DgEOEv4aMuO6MZplv/1kh4WeFC7SsnEX7bLext0QZITdBaL65dUN8Kt8G/ZeTG w3lQ01nBFqY= =InnO -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] [Python-3000] 2.6.1 and 3.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 19, 2008, at 3:19 PM, Terry Reedy wrote: Let's try this for 3.0rc4 then. The current release is rc2. Skipping rc3 would confuse people'-) Yeah, my calendar was wrong, but the PEP (and more importantly... code!) was right :). There is no rc4! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSScZWXEjvBPtnXfVAQKpQAQAi9Q8rfgcCVXmQ2tIqaiAVKOQHDPQdfhF lyDWHg+6i2EGrbs0Jju5GB9YML1yNga3X85zfQSedu6mgpA4dV6NvW988N3Wp4oG ztDGT7yLxwYe4Wy606FF6lxSlXSvXQRLc/Nf1qgn8dDGskQKO2LZ+fUHW0BIWDBN RFAuZqzdWQY= =9Z8w -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
[Python-Dev] RELEASED Python 3.0 final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On behalf of the Python development team and the Python community, I am happy to announce the release of Python 3.0 final. Python 3.0 (a.k.a. Python 3000 or Py3k) represents a major milestone in Python's history, and was nearly three years in the making. This is a new version of the language that is incompatible with the 2.x line of releases, while remaining true to BDFL Guido van Rossum's vision. Some things you will notice include: * Fixes to many old language warts * Removal of long deprecated features and redundant syntax * Improvements in, and a reorganization of, the standard library * Changes to the details of how built-in objects like strings and dicts work * ...and many more new features While these changes were made without concern for backward compatibility, Python 3.0 still remains very much Pythonic. We are confident that Python 3.0 is of the same high quality as our previous releases, such as the recently announced Python 2.6. We will continue to support and develop both Python 3 and Python 2 for the foreseeable future, and you can safely choose either version (or both) to use in your projects. Which you choose depends on your own needs and the availability of third-party packages that you depend on. Some other things to consider: * Python 3 has a single Unicode string type; there are no more 8-bit strings * The C API has changed considerably in Python 3.0 and third-party extension modules you rely on may not yet be ported * Tools are available in both Python 2.6 and 3.0 to help you migrate your code * Python 2.6 is backward compatible with earlier Python 2.x releases We encourage you to participate in Python 3.0's development process by joining its mailing list: http://mail.python.org/mailman/listinfo/python-3000 If you find things in Python 3.0 that are broken or incorrect, please submit bug reports at: http://bugs.python.org/ For more information, links to documentation, and downloadable distributions, see the Python 3.0 website: http://www.python.org/download/releases/3.0/ Enjoy, - -Barry Barry Warsaw [EMAIL PROTECTED] Python 2.6/3.0 Release Manager (on behalf of the entire python-dev team) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSTc3pXEjvBPtnXfVAQI69wP/dPHh8IL3GxziEV9QzlveKG+KyZb2X16x fxJnTCiXAbiAhT5C+m43OEnbF1PJgMDKtcZ5b7aQb4TQ0mJxISTQh0RfLCpArmlo tdTbzCLnh13KzB+3sUHCx+MeQNXERoWDV8hLz+4Ae71UsuUGynhtyP7ZJMJDue8j so2gv3fOMSs= =vkiy -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] RELEASED Python 3.0 final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 3, 2008, at 9:13 PM, Dotan Cohen wrote: On this page: http://www.python.org/download/releases/3.0/ The text This is a proeuction release should probably read This is a production release. It would give a better first impression :) Fixed, thanks! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSTc/WHEjvBPtnXfVAQL8TwP+M2Ryv7WY36ICEvzGU4EzlRG/gI4MolQe cD8DJUJfQuR6INTot/t7vTcL8oDHq7q9OHbfvd3jmSwH/ZytsMz2OvJUYlKDQjwG BcQRpioprcesoU6cufSmKAUiUP+L0RTAMmT0WDbbeCzzMZRq3Humd4Zs43nL26NT uFb83Dk6yWA= =qPjn -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] [Python-3000] RELEASED Python 3.0 final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 3, 2008, at 9:19 PM, Guido van Rossum wrote: Thanks so much for seeing this one through, Barry and co! Champagne!!! Now if only I could go on vacation. :) - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSTc/gXEjvBPtnXfVAQKZGgP/Y41JSlU6bQlGQKQmrjxv2jUWf2AWDLSu 4HG45m5plX/r6z1bZlxdqvpVqVRGgInoe+uw96WEgjW+F5NomU4ZKQ+YVOZFjkJY izAWQllxZRkErdIBq158DOKTTyiJpUpRnGvwx2J67/pIBGLfFLZ+yPAu+4jT4fJ+ qFq/oGKCKIY= =wiBX -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] RELEASED Python 3.0 final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 4, 2008, at 6:21 PM, Martin v. Löwis wrote: I can't find any docs built for Python 3.0 (not 3.1a0). The Windows installation has new 3.0 doc dated Dec 3, so it was built, just not posted correctly. That doesn't mean very much. I built it on my local machine. Anybody with subversion and python could do that; the documentation is in subversion. Whether or not it appears on the web site as part of the release process is an entirely different matter. It used to be that the doc maintainer (Fred Drake) was part of the release team and release process. I think Georg is complaining that he is release maintainer, but not part of the release process. I've asked Georg to update PEP 101 to make his role as Documentation Expert explicit. Unfortunately we only debug major releases once (or twice) every 18 months. But next time, we'll get that part right for sure! In the meantime, I'll make sure Georg is involved in point releases moving forward. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSThm8HEjvBPtnXfVAQJgGgP/eiAUroHbxvpJLT8JRpW5H+nmyU5yGGCY NZYrU/Vm2vRPFyfDevOFErQX9Jr1LqO0x4Qgxm4PpIj3OVwM16INz98as6nONEhC MfTjf8Pp7f5BrF7HYh1XfPqTy5qpVhAkzKrCcjUk2VT/JHzJ4wrAl+29VhDTjvrz 3SXphnxWi6w= =dfm7 -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
[Python-Dev] RELEASED Python 2.6.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hot on the heals of Python 3.0 comes the Python 2.6.1 bug-fix release. This is the latest production-ready version in the Python 2.6 family. Dozens of issues have fixed since Python 2.6 final was released in October. Please see the NEWS file for details: http://www.python.org/download/releases/2.6.1/NEWS.txt For more information on Python 2.6 please see http://docs.python.org/dev/whatsnew/2.6.html Source tarballs and Windows installers can be downloaded from the Python 2.6.1 page: http://www.python.org/download/releases/2.6.1/ Bugs can be reported in the Python bug tracker: http://bugs.python.org Enjoy, - -Barry Barry Warsaw [EMAIL PROTECTED] Python 2.6/3.0 Release Manager (on behalf of the entire python-dev team) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSTi3KnEjvBPtnXfVAQLhQAP7BR8eqlVLDlu/bp2tGaRRQS8GW5X8KQQk h0RwCcAKK19WH6YS6zH+VoIpD8LnD37YqZL3m5MQZ/rDf0o3e6152CZ6GJvWE+0i 6w0cSvDqdWuOpfUfpYR21eQnoFuC6x/yfI//yWCnu8bZCypjmJCLKZAvu4pMjYgD ceChg4lLE68= =u/iW -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] 3.0.1 possibilities
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 6, 2008, at 6:25 PM, Guido van Rossum wrote: On Sat, Dec 6, 2008 at 3:18 PM, Benjamin Peterson [EMAIL PROTECTED] wrote: Since the release of 3.0, several critical issues have come to our attention. Namely, the builtin cmp function wasn't removed [1] and the new IO library proved to be (as expected) abysmally slow [2][3][4]. Christian proposed that we release 3.0.1 within the next week to patch up this critical issues. Thoughts? [1] http://bugs.python.org/1717 [2] http://bugs.python.org/4533 [3] http://bugs.python.org/4561 [4] http://bugs.python.org/4565 I've set the priority on all these to release blockers, but I have my reservations about 4561 and 4565. Resolution of those seem like more than a week or so away. If we want to do a bug fix release for 3.0.1, I'd like to do it no later than the 19th. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSTsNtXEjvBPtnXfVAQKI4AP8CNQEEb2KuN8cvd+t6YK39jFPxEo8j/YV 022zAWX3nNgj/R88C7OwoP6nYLx+zz4D3USj65OZN4NS9W9tJYKs+Lv6CnjIJi2X cVceihcJHVYbyx8r14mYt6VjSmpTuNBD8uPZGv23WLZJZ5pNpWeuEMqI6XR27bY2 NYxbwSEUQpw= =3wZN -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] 3.0.1 possibilities
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 7, 2008, at 7:05 PM, Christian Heimes wrote: Martin v. Löwis wrote: I think it is still timely when fixed in January or February. In fact, releasing it still in December might not be possible, due to the limited time available. The cmp() / PyObject_Compare() removal patch is almost done. With some help I can finish it until Tuesday evening. We can have another release by Monday Dec 15th. Python 3.0.0 has some defects that should be fixed before people are spending their Xmas holidays with 3.0. The defects include * cmp(), PyObject_Compare() and frieds * global/nonlocal shortcuts (global x = 0) aren't working * unnecessary slowdown of read() due slow buffer resizing. An early 3.0.1 release makes it possible to sync 2.6 and 3.0 relases again. If we release it now we can have an combined release of 2.6.2 and 3.0.2 in two months from now. Two months are quite some time to fix the performance issue of the new IO library. If Guido and Barry are fine with a lax policy on performance fixes we can integrate more tweaks. I believe performances patches were considered as features in the past. For this reason they weren't allowed for minor releases. Mark's work on long integer optimizations and json speedup are good candidates. I'm personally okay with performance fixes in point releases, as long it doesn't change API or add additional features. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSTxv5XEjvBPtnXfVAQIu6AQAkxyGwhapcREx5/E3yHUf8lWvM4lh/FdR AfHwwp7hs+yX8rR05CWAUfllY9dHcHKHvBCwTCgfuIrc4GJWbJHcx9/b19GTpzre 7fcikjQ0sk6zUq85DiJah7qL5AkA6Jmiby+rol7iudHlmQO/+6F6+aeL+vSKG8IC vYbLILAFapI= =ScYg -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] 3.0.1 possibilities
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 7, 2008, at 7:56 PM, Christian Heimes wrote: Barry Warsaw wrote: I'm personally okay with performance fixes in point releases, as long it doesn't change API or add additional features. Does your okay include or exclude new internal APIs like new helper functions or a new C modules? I /personally/ don't have a problem with that, but we need consensus before that becomes policy. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBST0c7nEjvBPtnXfVAQJvQwQAjrCuivCuLT3HNq6n5VvUKVkxto5wyBzW ka9YuFoBCVRDt7Z7Sn59UeLGVgrsL9Zw2rSra4cXE/1QaUzpxJlaFpafWVJilCPh +hv6/t6ky0Ww0FsEv+56SRHOVRlfqgNMIbmDXemf40Oo/IYxqNL5HP59NeIvk0oa u3Mmc7qsP1k= =ZK8M -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] 3.0.1 possibilities
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 8, 2008, at 3:39 PM, Antoine Pitrou wrote: Nick Coghlan ncoghlan at gmail.com writes: Where would adding a (undocumented) get_filename() method to ZipImporter objects for the benefit of the -m switch fit then? Why not call it _get_filename() in 3.0 and get_filename() in 3.1? +1 - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBST2LKXEjvBPtnXfVAQJZzAP/avX4YgpBSmOAh6Zc2TZEnsllRz6CRa86 bEPCWF1an7H9zzDl6gS5ZjbstXoEPf0Irr+W6BTSLVnRT/G7rFgw5q/QlG2yqvCP dgOCT1Vr3PXgXouNkGaBFI5L/Aw2fuDadWUpGeA3FgH3PxaAH0XAr5LcKP2SidXc v5nDim8lCxc= =k3gW -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] [Python-3000] python-3000 list is closed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 15, 2008, at 7:44 PM, s...@pobox.com wrote: Martin The mailing list python-3...@python.org is now closed. All Martin further discussion of Python 3.x takes place on Martin python-...@python.org. Maybe set up a simple email alias reflecting python-3000 to python- dev? Or, https://launchpad.net/replybot - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSUb/R3EjvBPtnXfVAQJ4sgP/Wy8ma4nzcYQ5gXVCw2TpODq5l/duzB+I f3ej5tSyvI2wzf+OTQQwth5A0xySB8LoGbSQsYwhvbA+3xXOe1lIYeVYUGru9Y4T xs1axRgydTwxAFgHBdjrY7tLhXH4GOed0xYvbu6b3tRslb+4agmOhluX4WCBRZH+ sgIW0XL7nsI= =Nrdo -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
[Python-Dev] Python 3.0.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'd like to get Python 3.0.1 out before the end of the year. There are no showstoppers, but I haven't yet looked at the deferred blockers or the buildbots. Do you think we can get 3.0.1 out on December 24th? Or should we wait until after Christmas and get it out, say on the 29th? Do we need an rc? This question goes mostly to Martin and Georg. What would work for you guys? - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSUwgEXEjvBPtnXfVAQIthgP7BDS6xfBHhADKc50ANvZ5aAfWhGSU9GH/ DR+IRduVmvosu9gm92hupCOaLCN4IbtyFx27A8LQuPNVc4BVrhWfDKDSzpxO2MJu xLJntkF2BRWODSbdrLGdZ6H6WDT0ZAhn6ZjlWXwxhGxQ5FwEJb7moMuY7jAIEeor 5n6Ag5zT+e8= =oU/g -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] Python 3.0.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 19, 2008, at 5:42 PM, Nick Coghlan wrote: Barry Warsaw wrote: I'd like to get Python 3.0.1 out before the end of the year. There are no showstoppers, but I haven't yet looked at the deferred blockers or the buildbots. Do you think we can get 3.0.1 out on December 24th? Or should we wait until after Christmas and get it out, say on the 29th? Do we need an rc? There are some memoryview issues [1] I'd like to have fixed for 3.0.1 - the 29th would be a much easier date to hit. A quick review pass through the other 3.0 highs and criticals might also be worthwhile. Thanks. I've bumped that to release blocker for now. If there are any other 'high' bugs that you want considered for 3.0.1, please make the release blockers too, for now. - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSUwkRnEjvBPtnXfVAQKQ4QP/eRmWBgyuijbe9vnXkRkTkAmd4qyrAD2s Forp4hKGvoc4A03Q4x2uVweI4oSdFrKIN2NlcM3JVlSrsU07DTElFoCEA/A8DB3N +6Sp9bC98iVqGUmle54rFIm0F/iCoFQ59mp9jNGeiKVwjojUDkbJNXulHuYIb1co RuICfsatRc0= =zjQz -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
