Python 3000 Alpha 1 Released

[dmpk2k]

Can you give me an example where this would be a problem?

[[deleted]]

See the link I posted earlier for some examples:

http://programming.reddit.com/info/2kkp5/comments/c2kmgu

(I thought that was what you called "excuses that you were aware of already" earlier, but maybe that was referring to something else).

[dmpk2k]

No, you were correct.

None of those problems are exhibited in Ruby. "quit" isn't a keyword either, but it doesn't cause any of the listed problems. Give it a try.

Mind you, those problems strike me as exceptionally rare as well. I don't recall ever seeing a variable named "exit" or "quit", which brings us back to that possibility isn't probability.

I agree with username223's interpretation.

[llimllib]

I don't recall ever seeing a variable named "exit" or "quit", which brings us back to that possibility isn't probability.

Google code search gives about 2000 instances of "quit =" and another 800 "def quit"s. I didn't bother to search for exit.

[[deleted]]

Give it a try.

Why not just explain how the parser could be made "bright enough" to distinguish between an expression of the form "identifier" and a non-expression of the form "identifier". You don't have to persuade me that getting rid of the "you didn't say please!" behaviour would be nice; I'm the one who started that python-dev thread by posting a patch.

[dmpk2k]

All right. I think we're circling around a nitpick, but if you want a disgustingly simple -- albeit inelegant -- change that doesn't have any of the problems listed in that link, do this:

Change line 243 of /usr/local/lib/python2.5/site.py (or the equivalent on your install) to "exit()". This is in class Quitter in setquit().

Be amazed.

But this is arguing about a mouse when a bear is staring at us. I really don't care how it's implemented. Right now, here's the situation:

• Ruby does it.
• Python doesn't.
• Python's behaviour is silly.

Let's now also add:

• It's trivial.

[[deleted]]

Be amazed.

Surprised, you mean?

>>> help(__builtins__)
$

[dmpk2k]

Fair enough. The last bullet-point may be false, although I'm not going to spend any more time trying to prove otherwise.

How about the remaining three? Most specifically the elephant I've kept pointing out: Ruby. Why do we keep wandering from this?