Re: [Python-Dev] expy: an expressway to extend Python
Yingjie Lan wrote: This is to announce the initial release of expy 0.1.0. More details at http://expy.sourceforge.net/ I'm clearly biased, but my main concern here is that expy requires C code to be written inside of strings. There isn't any good editor support for that, so I doubt that expy is good for anything but very thin wrappers (as in the examples you presented). That said, you might want to look at the argument unpacking code generated by Cython. It's highly optimised through specialisation and has been benchmarked quite a bit faster than the generic Python C-API functions for tuple/keyword extracting. Since argument conversion seems to be more or less all that expy really does, maybe you want to reuse that code. Stefan ___ 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] (try-except) conditional expression similar to (if-else) conditional (PEP 308)
Steven D'Aprano writes: It's not immediately obvious to me why the last expression should be given that privileged rule. Why not the first expression? Or the second, for that matter. So find a large body of Lisp code and run grep -r prog1 | wc, grep -r prog2 | wc, and grep -r progn | wc on it. I think the pragmatic answer will be obvious. Personally, I like functional languages and style. But I admit the *need* for a progn construct (ie, block) to express procedural style, and see no particular reason why expressing that by making a syntactic distinction between expressions and statements is worse (or better) than the progn construct. That should be kept distinct from the question of whether extended assignment operators or conditional operators are appropriate for a given language. ___ 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] (try-except) conditional expression similar to (if-else) conditional (PEP 308)
On 8 Aug 2009, at 08:02 , Steven D'Aprano wrote: On Fri, 7 Aug 2009 08:22:14 pm Kristján Valur Jónsson wrote: Unless I am very much mistaken, this is the approach Ruby takes. Everything is an expression. For example, the value of a block is the value of The last expression in the block. Copying what other languages do is not necessarily a bad thing, but that would fail both explicit is better than implicit and in the face of ambiguity, avoid the temptation to guess. The first objection one might be able to give, you maybe, but the second one? Where's the ambiguity in compound statements return the result of the last evaluated expression? It's not immediately obvious to me why the last expression should be given that privileged rule. Why not the first expression? Because it wouldn't make any sense? When you're computing something, the value you want is the one at the end of the computation (usually called a result), not some random one somewhere else. ___ 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] www/svn python.org status update
The following sites are up again on a new machine, but cannot be updated through SVN hooks or whatever mechanism: www.python.org docs.python.org www.jython.org planet.python.org planet.jython.org svn.python.org was deliberately not brought up again. The backups were a few hours behind and missing the ~10 most recent commits. Not disastrous, but it could probably mess up people's SVN trees, so after some IRC discussion, the decision was to wait until the original disks are available again. That will probably not occur until Monday, maybe Tuesday. I've disabled donations to the PSF through credit cards, which pointed to a CGI script that doesn't currently work; PayPal donations still work. Do we want to make any edits to the 3.1 or 3.0 pages about the I/O bug? I can do that manually if someone will provide the text and/or a patch to put up. Unfortunately without SVN we probably can't cut a new 3.1 release, unless Benjamin or someone has a really up-to-date copy of the Mercurial tree and wants to work from that. --amk ___ 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] www/svn python.org status update
On Sat, Aug 8, 2009 at 22:22, A.M. Kuchlinga...@amk.ca wrote: svn.python.org was deliberately not brought up again. The backups were a few hours behind and missing the ~10 most recent commits. Not disastrous, but it could probably mess up people's SVN trees, so after some IRC discussion, the decision was to wait until the original disks are available again. That will probably not occur until Monday, maybe Tuesday. What's the last revision supposed to be? I keep a somewhat regularly updated full sync of the Python repo. Cheers, Dirkjan ___ 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] www/svn python.org status update
What's the last revision supposed to be? I keep a somewhat regularly updated full sync of the Python repo. We don't know exactly; python-checkins has recorded r74352. If anybody has a more recent checkout (svn info .), please speak up. 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] www/svn python.org status update
The following sites are up again on a new machine I'd like to thank the people who have helped getting the temporary machine up: Thomas Wouters spent much of his day at XS4ALL, where he was helped by Gerben Schepers (who also provided the hardware). Sean Reifschneider provided the backups (from the system at tummy.com which keeps backups of all python.org machines). Andrew Kuchling put the backup back into the places to bring the system into its current state. The failure of the old system was caused by the RAID controller; the disks themselves should still be intact. Unfortunately, the RAID controller keeps its configuration on the controller (not on the disks), so it is unclear still whether the replacement will be able to recognize the RAID array. 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
