Re: [Python-Dev] PEP 3003 - Python Language Moratorium

2009-11-07 Thread Willem Broekema
On Sun, Nov 8, 2009 at 1:16 AM, Steven D'Aprano st...@pearwood.info wrote: Willem, the rationale for this PEP is to give alternative implementations the chance to catch up with CPython. Given your statement that CLPython is quite complete on the language level, but missing standard library

Re: [Python-Dev] PEP 3003 - Python Language Moratorium

2009-11-06 Thread Willem Broekema
On Fri, Nov 6, 2009 at 6:18 AM, Steven D'Aprano st...@pearwood.info wrote: I don't know how mature or active it is, so it may not count as either major or complete, but there's also CLPython: http://common-lisp.net/project/clpython/ CLPython is in steady development, quite complete and stable

Re: [Python-Dev] PEP about sys.implementation and implementation specific user site directory

2009-10-10 Thread Willem Broekema
On Sat, Oct 10, 2009 at 1:29 AM, Christian Heimes li...@cheimes.de wrote: I'm proposing two new attributes in the sys module: sys.implementation and sys.userdirsuffix. This seems like a good idea. I'm not sure this idea will easily be accepted, but I'd like to see the sys module eventually

Re: [Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations

2009-09-22 Thread Willem Broekema
On Tue, Sep 22, 2009 at 5:12 PM, Mark Dickinson dicki...@gmail.com wrote: - Exception to the previous item: if the left operand is an instance of a built-in type or a new-style class, and the right operand is an instance of a proper subclass of that type or class AND overrides the base’s

Re: [Python-Dev] Avoiding file descriptors leakage in subprocess.Popen()

2009-06-16 Thread Willem Broekema
On Tue, Jun 16, 2009 at 1:21 PM, Michael Foordfuzzy...@voidspace.org.uk wrote: Steven D'Aprano wrote: On Tue, 16 Jun 2009 01:20:53 pm Cameron Simpson wrote: I don't think all pythons do immediate ref-counted GC. Jython and IronPython don't. I don't know about PyPy, CLPython, Unladen Swallow,

Re: [Python-Dev] yield * (Re: Missing operator.call)

2009-02-07 Thread Willem Broekema
On Sat, Feb 7, 2009 at 10:04 AM, Greg Ewing greg.ew...@canterbury.ac.nz wrote: def f(): v = yield *g() print v def g(): yield 42 return spam Function g violates the current limitation that generators can't return with a value. So can g only be used using yield * then, or

[Python-Dev] effect of exec on local scope

2008-10-08 Thread Willem Broekema
The issue came up while trying to get some Sympy code running on CLPython. class C: exec a = 3 print locals() 1. Is it guaranteed that class C gets an attribute a, i.e. that the locals printed include {'a': 3}? 2. It it (also) guaranteed if it were in a function scope? The complete syntax of

Re: [Python-Dev] bug or a feature?

2008-06-12 Thread Willem Broekema
On Thu, Jun 12, 2008 at 2:56 PM, Carl Friedrich Bolz [EMAIL PROTECTED] wrote: Of course attribute name lookups are affected, because you can have a non-string key that has a __hash__ and __eq__ method to make it look sufficiently like a string to the dict. Then the attribute lookup needs to

Re: [Python-Dev] bug or a feature?

2008-06-12 Thread Willem Broekema
On Thu, Jun 12, 2008 at 9:46 PM, Guido van Rossum [EMAIL PROTECTED] wrote: The intention was for these dicts to be used as namespaces. I think of it as follows: (a) Using non-string keys is a no-no, but the implementation isn't required to go out of its way to forbid it. That will allow

Re: [Python-Dev] Problem with super() usage

2006-07-18 Thread Willem Broekema
On 7/18/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: C++ originally specified multiple inheritance, but it wasn't cooperative in the sense that super is. In Lisp, though, where cooperative method dispatch originated, call-next-method does basically the same thing in the case where there's

Re: [Python-Dev] Exception Reorg PEP checked in

2005-08-04 Thread Willem Broekema
On 8/4/05, Brett Cannon [EMAIL PROTECTED] wrote: OK, once the cron job comes around and is run, http://www.python.org/peps/pep-0348.html will not be a 404 but be the latest version of the PEP. Currently, when the recursion limit is reached, a RuntimeError is raised. RuntimeError is in the PEP

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-02 Thread Willem Broekema
On 8/2/05, Stephen J. Turnbull [EMAIL PROTECTED] wrote: I don't see it that way. Rather, Raisable is the closest equivalent to serious-condition, and CriticalException is an intermediate class that has no counterpart in Lisp usage. That would imply that all raisables are 'serious' in the Lisp

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-01 Thread Willem Broekema
On 7/31/05, Brett Cannon [EMAIL PROTECTED] wrote: On 7/31/05, Willem Broekema [EMAIL PROTECTED] wrote: I does not seem right to me to think of KeyboardInterrupt as a means to cause program halting. An interpreter could in principle recover from it and resume execution of the program

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-08-01 Thread Willem Broekema
On 8/1/05, Stephen J. Turnbull [EMAIL PROTECTED] wrote: Uh, according to your example in Common LISP it is indeed an error, I think you are referring to the first word of this line: Error: Received signal number 2 (Keyboard interrupt) [condition type: INTERRUPT-SIGNAL] Well, that refers to

Re: [Python-Dev] Pre-PEP: Exception Reorganization for Python 3.0

2005-07-31 Thread Willem Broekema
On 7/31/05, Brett Cannon [EMAIL PROTECTED] wrote: While we do tend to use KeyboardInterrupt as a way to kill a program, is that really control flow, or a critical exception that the program needs to stop because an serious event occurred? I does not seem right to me to think of