[Python-Dev] What's New in Python 3.3
Hello all, I'll soon be starting the edits of Whatsnew for 3.3. When I did this for 3.2, it took over 150 hours of work to research all the changes. This time there are many more changes, so my previous process won't work (reviewing every new in 3.3 entry in the docs, every entry in the voluminous Misc/NEWS file, etc). You can help out by checking-in draft entries for your favorite new features. That way, I can avoid the time consuming curation step and focus on the text, organization, and examples. I appreciate your help, Raymond ___ 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] SPARC testers (and buildbot!) needed
Hello, currently the only cheap way for developers to test on SPARC that I'm aware of is using this old Debian qemu image: http://people.debian.org/~aurel32/qemu/sparc/ That image still uses linuxthreads and may contain any number of platform bugs. It is currently impossible to run the test suite without bus errors, see: http://bugs.python.org/issue15589 Could someone with access to a SPARC machine (perhaps with a modern version of Debian-sparc) grab a clone from http://hg.python.org/cpython/ and run the test suite? Also, it would be really nice if someone could donate a SPARC buildbot. Stefan Krah ___ 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] Understanding the buffer API
Nick Coghlan ncogh...@gmail.com wrote: It does place a constraint on consumers that they can't assume those fields will be NULL just because they didn't ask for them, but I'm struggling to think of any reason why a client would actually *check* that instead of just assuming it. Can we continue this discussion some other time, perhaps after 3.3 is out? I'd like to respond, but need a bit more time to think about it than I have right now (for this issue). Stefan Krah ___ 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] SPARC testers (and buildbot!) needed
Could someone with access to a SPARC machine (perhaps with a modern version of Debian-sparc) grab a clone from http://hg.python.org/cpython/ and run the test suite? I'd invoke the scratch your own itch principle here. SPARC, these days, is a minority platform; I wouldn't mind deleting all SPARC support from Python in some upcoming release. In no way I feel obliged to take efforts that Python 3.3 works on SPARC (and remember that it was me who donated the first buildbot slave, and that was a SPARC machine - which I now had to take down, ten years later). Of course, when somebody has access to SPARC hardware, *and* they have some interest that Python 3.3 works on it, they should test it. But testing it as a favor to the community is IMO irrelevant now; that particular community is shrinking rapidly. What I personally really never cared about is SparcLinux; if sparc, then it ought to be Solaris. IOW: if it breaks, no big deal. Someone may or may not contribute a patch. Regards, Martin ___ 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] What's New in Python 3.3
On Wed, Aug 8, 2012 at 12:54 AM, Raymond Hettinger raymond.hettin...@gmail.com wrote: Hello all, I'll soon be starting the edits of Whatsnew for 3.3. When I did this for 3.2, it took over 150 hours of work to research all the changes. This time there are many more changes, so my previous process won't work (reviewing every new in 3.3 entry in the docs, every entry in the voluminous Misc/NEWS file, etc). Thanks for all of this work! And thanks to A.M. Kuchling and everyone else that goes through the effort to make the What's new in Python documents so great. They are my high level roadmap for re-implementing in Jython. It would be so much harder without them. -Frank ___ 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] SPARC testers (and buildbot!) needed
Le 08/08/2012 15:25, Martin v. Löwis a écrit : Of course, when somebody has access to SPARC hardware, *and* they have some interest that Python 3.3 works on it, they should test it. But testing it as a favor to the community is IMO irrelevant now; that particular community is shrinking rapidly. What I personally really never cared about is SparcLinux; if sparc, then it ought to be Solaris. What Martin said; SPARC under Linux is probably a hobbyist platform. Enterprise users of Solaris SPARC systems can still volunteer to provide and maintain a buildslave. Regards Antoine. ___ 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] What's New in Python 3.3
Does Python 3.3 support cross-compilation? There are two new option for configure: --host and --build, but it's not mentioned in What's New in Python 3.3. Victor ___ 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] SPARC testers (and buildbot!) needed
On 8 August 2012 18:56, Antoine Pitrou solip...@pitrou.net wrote: Le 08/08/2012 15:25, Martin v. Löwis a écrit : Of course, when somebody has access to SPARC hardware, *and* they have some interest that Python 3.3 works on it, they should test it. But testing it as a favor to the community is IMO irrelevant now; that particular community is shrinking rapidly. What I personally really never cared about is SparcLinux; if sparc, then it ought to be Solaris. What Martin said; SPARC under Linux is probably a hobbyist platform. Enterprise users of Solaris SPARC systems can still volunteer to provide and maintain a buildslave. Is http://wiki.python.org/moin/BuildBot the relevant documentation? It still seems to refer to subversion, I presume that is no longer needed and just mercurial will do? I've set up a blank solaris 10 zone on a sparc T1000 with the OpenCSW toolchain (gcc 4.6.3) on our server and installed buildslave. According to the instructions this is the point where I ask for a slave name and password. Also, would it make sense to support OpenCSW more out of the box? Currently we carry some patches for setup.py in order to pick up e.g. sqlite from /opt/csw etc. Would there be an interest in supporting this? Regards, Floris ___ 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
