Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Neal Norwitz
On 7/10/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote: > Jeremy Hylton wrote: > > > To express this email in the positive form: > > 1. Reserved words should be real words. > > 2. The meaning of the word should be clear. > > 3. "Put statements in positive form." (Strunk & White) > > 4. The word shoul

[Python-Dev] easy_install

2006-07-10 Thread Talin
Here's something to discuss: First, let me say that I love easy_install. I absolutely "just works" and does what I want, and makes it really simple to install whatever bit of Python code I need. At the same time, however, I get kind of scared when I hear people on the list discussing the vario

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Fredrik Lundh
Talin wrote: > I also think that it won't be a complete disaster if we do nothing at > all - there *are* existing ways to deal with this problem; there are > even some which aren't hackish and non-obvious. For example, its easy > enough to create an object which acts as an artificial scope: >

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Fredrik Lundh
Jeremy Hylton wrote: > To express this email in the positive form: > 1. Reserved words should be real words. > 2. The meaning of the word should be clear. > 3. "Put statements in positive form." (Strunk & White) > 4. The word should sound good. agreed. a word should describe what a thing is, no

Re: [Python-Dev] Klocwork analysis of source if we want it

2006-07-10 Thread Martin v. Löwis
Brett Cannon wrote: > http://www.klocwork.com/company/releases/06_26_06.asp > > Looks like Klocowork is doing the same thing as Coverity and providing > free static analysis of source for open source projects. Doubt we want > this *and* Coverity, but figured wouldn't hurt to let people know about

Re: [Python-Dev] In defense of Capabilities [was: doc for new restricted execution design for Python]

2006-07-10 Thread Talin
Brett Cannon wrote: > Using a factory method callback, one could store the PyCodeObject in a C > proxy object that just acts as a complete delegate, forwarding all method > calls to the internally stored PyCodeObject. That would work. > > > For this initial implementation, though, I am not going

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Talin
Ka-Ping Yee wrote: > On Mon, 10 Jul 2006 [EMAIL PROTECTED] wrote: > >>I think Talin's got a point though. It seems hard to find one short English >>word that captures the essence of the desired behavior. None of the words >>in his list seem strongly suggestive of the meaning to me. I suspect th

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Mike Krell
On 7/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I don't think the keyword should indicate a scope. > I'd prefer it if LOAD_ just percolated its way up the chain of > cells (or could be identified at compile time by inspecting the AST as I > think Guido intends) without the programmer ha

Re: [Python-Dev] Doctest and Footnotes

2006-07-10 Thread Phillip J. Eby
At 11:36 PM 7/10/2006 -0400, Benji York wrote: >The footnote code is executed every time the footnote is referenced, and >is /not/ executed at any other time (i.e. it's not executed at the point >the footnote is defined). A warning is generated if a footnote (that >includes code) is defined but ne

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread skip
>> What's wrong with "nonlocal"? I don't think i've seen an argument >> against that one so far (from Talin or others). Mike> It sounds a bit awkward to me. Also, it would be nice if the Mike> keyword indicated which scope was operative. Sounds awkward to me as well. Couldn't

[Python-Dev] Doctest and Footnotes

2006-07-10 Thread Benji York
A coworker of mine (Gary Poster) had a really good idea a couple weeks ago: teach doctest about ReST-style footnotes. I implemented it over the weekend and brought it to Tim Peter's attention today. Tim generally liked the idea and suggested I bring it up here. Here's the idea: when a footnot

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Ka-Ping Yee
On Mon, 10 Jul 2006, Jeremy Hylton wrote: > The current use of global meets the requirements. The meaning there > is clear, because global means global namespace. If purple were a > keyword, I wouldn't know what it means. I was not proposing the use > of global for some other meaning (and though

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Matthew Barnes
On Mon, 2006-07-10 at 16:43 -0400, Jeremy Hylton wrote: > To express this email in the positive form: > 1. Reserved words should be real words. > 2. The meaning of the word should be clear. > 3. "Put statements in positive form." (Strunk & White) > 4. The word should sound good. As I've been foll

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Jeremy Hylton
On 7/10/06, Ka-Ping Yee <[EMAIL PROTECTED]> wrote: > On 7/10/06, Ka-Ping Yee <[EMAIL PROTECTED]> wrote: > > What's wrong with "nonlocal"? I don't think i've seen an argument > > against that one so far (from Talin or others). > > On Mon, 10 Jul 2006, Jeremy Hylton wrote: > > It's a made-up word.

[Python-Dev] Support for PyGetSetDefs in pydoc

2006-07-10 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patch #1520294 adds support for attributes defined with PyGetSetDef in extension modules to pydoc, specifically so things like help (array.array.typecode) gives something useful, like the attribute's docstring for instance. Along the way, I added

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Tim Peters
[Scott Dial] > Wouldn't this function be better named sys._getframes since we already > have a sys._getframe for getting the current frame? http://mail.python.org/pipermail/python-dev/2005-March/051887.html The first & only name suggested won. As it says there, I usually have no appetite for

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Greg Ewing
Mike Krell wrote: > If I've followed the discussions correctly, I think the parent scope > would be operative, so I humbly suggest "parent". -1, this is far too commonly used as a variable name. -- Greg ___ Python-Dev mailing list Python-Dev@python.org

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Greg Ewing
Guido van Rossum wrote: > Then let's allow > > nonlocal x = 12 > > as a shortcut for > > nonlocal x > x = 12 I thought you didn't like that, because in nonlocal x = 12 x = 42 it's not clear whether these are talking about the same x or not. -- Greg __

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Almann T. Goo
On 7/10/06, Jeremy Hylton <[EMAIL PROTECTED]> wrote: On 7/10/06, Ka-Ping Yee <[EMAIL PROTECTED]> wrote:> On Mon, 10 Jul 2006 [EMAIL PROTECTED] wrote:> > I think Talin's got a point though.  It seems hard to find one short English > > word that captures the essence of the desired behavior.  None of

Re: [Python-Dev] User's complaints

2006-07-10 Thread Guido van Rossum
Not to mention the cost to documentation and books everywhere -- updating our own docs is only the tip of the iceberg. And then updating the users' brains is an even bigger job... (Though at least it is highly parallellizable. :-) --Guido On 7/10/06, A.M. Kuchling <[EMAIL PROTECTED]> wrote: > On

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Ka-Ping Yee
On 7/10/06, Ka-Ping Yee <[EMAIL PROTECTED]> wrote: > What's wrong with "nonlocal"? I don't think i've seen an argument > against that one so far (from Talin or others). On Mon, 10 Jul 2006, Jeremy Hylton wrote: > It's a made-up word. You won't find it in the dictionary and the > google define: q

Re: [Python-Dev] Fix for Lib/test/leakers/test_gestalt.py

2006-07-10 Thread Thomas Heller
Thomas Heller schrieb: > I think this fixes the leak in Lib/test/leakers/test_gestalt.py. > > Index: Python/mactoolboxglue.c > === > --- Python/mactoolboxglue.c (revision 50522) > +++ Python/mactoolboxglue.c (working copy) > @@ -6

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Raymond Hettinger
Anthony Baxter wrote: But, the imagined costs of a new feature during beta are illusory. This, I cannot agree with. The costs and risks of just continuing to add new features all through the release process are high. I meant this particular feature. In general, there ough

[Python-Dev] Klocwork analysis of source if we want it

2006-07-10 Thread Brett Cannon
http://www.klocwork.com/company/releases/06_26_06.aspLooks like Klocowork is doing the same thing as Coverity and providing free static analysis of source for open source projects.  Doubt we want this *and* Coverity, but figured wouldn't hurt to let people know about it. -Brett

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Anthony Baxter
On Tuesday 11 July 2006 06:52, Tim Peters wrote: > > I don't think trying to produce the most stable and bugfree > > Python possible could in _anyway_ be considered "pedantry", and > > it makes me quite grumpy to have it described in that way. > > He meant that "no new features", while a useful gui

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Tim Peters
[Raymond] >> FWIW, I think this patch should go in. The benefits are >> obvious and real. [Anthony Baxter] > Yep. I'm going to check it in, unless someone else beats me to it in > the next couple of hours before the b2 freeze. I'll merge it from my branch right after I send this email. It still

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Mike Krell
> What's wrong with "nonlocal"? I don't think i've seen an argument > against that one so far (from Talin or others). It sounds a bit awkward to me. Also, it would be nice if the keyword indicated which scope was operative. If I've followed the discussions correctly, I think the parent scope wo

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Anthony Baxter
On Tuesday 11 July 2006 06:16, Raymond Hettinger wrote: > FWIW, I think this patch should go in. The benefits are > obvious and real. Yep. I'm going to check it in, unless someone else beats me to it in the next couple of hours before the b2 freeze. > But, the imagined costs of a new feature >

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Jeremy Hylton
On 7/10/06, Ka-Ping Yee <[EMAIL PROTECTED]> wrote: > On Mon, 10 Jul 2006 [EMAIL PROTECTED] wrote: > > I think Talin's got a point though. It seems hard to find one short English > > word that captures the essence of the desired behavior. None of the words > > in his list seem strongly suggestive

Re: [Python-Dev] User's complaints

2006-07-10 Thread A.M. Kuchling
On Mon, Jul 10, 2006 at 05:13:53PM +0200, Armin Rigo wrote: > didn't draw much applause. It certainly gave me the impression that > many changes in Python are advocated and welcomed by only a small > fraction of users. The benefits of changes are usually clear, but I don't think the costs of chan

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread Ka-Ping Yee
On Mon, 10 Jul 2006 [EMAIL PROTECTED] wrote: > I think Talin's got a point though. It seems hard to find one short English > word that captures the essence of the desired behavior. None of the words > in his list seem strongly suggestive of the meaning to me. I suspect that > means one's ultimat

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Guido van Rossum
+1 On 7/10/06, Raymond Hettinger <[EMAIL PROTECTED]> wrote: > > Tim Peters wrote: > [Neal Norwitz] > > > There hasn't been much positive response (in the original thread or > here). > > Do note that there was little response of any kind, but all it got was > positive. It's not sexy, but is ess

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Raymond Hettinger
Tim Peters wrote: [Neal Norwitz] There hasn't been much positive response (in the original thread or here). Do note that there was little response of any kind, but all it got was positive. It's not sexy, but is essential for debugging deadlocks. If you ask for positive

Re: [Python-Dev] Discussion on Lib/test/crashers/

2006-07-10 Thread Brett Cannon
On 7/10/06, Raymond Hettinger <[EMAIL PROTECTED]> wrote: Brett Cannon wrote:> As I am sure some have noticed, as part of my dissertation I have been> trying to fix the various crashers.Nice project.One quick thought:  Any crasher that relies on gc.get_referrers() shouldnot be considered a bug.Righ

Re: [Python-Dev] Discussion on Lib/test/crashers/

2006-07-10 Thread Raymond Hettinger
Brett Cannon wrote: > As I am sure some have noticed, as part of my dissertation I have been > trying to fix the various crashers. Nice project. One quick thought: Any crasher that relies on gc.get_referrers() should not be considered a bug. The codebase should not be convoluted, complexifi

Re: [Python-Dev] Add new PyErr_WarnEx() to 2.5?

2006-07-10 Thread Tim Peters
As noted in http://mail.python.org/pipermail/python-dev/2006-May/065478.html it looks like we need a new Python C API function to make new warnings from the struct module non-useless. For example, runnning test_zipfile on Windows now yields """ test_zipfile C:\Code\python\lib\struct.py:63: D

[Python-Dev] Discussion on Lib/test/crashers/

2006-07-10 Thread Brett Cannon
As I am sure some have noticed, as part of my dissertation I have been trying to fix the various crashers.  I currently have some patches in SF for some of the crashers.  The other ones Armin and I have been talking, while others I have not started yet.  Review for the patches or help with fixing t

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Tim Peters
[Neal Norwitz] > There hasn't been much positive response (in the original thread or > here). Do note that there was little response of any kind, but all it got was positive. It's not sexy, but is essential for debugging deadlocks. If you ask for positive response, you'll get some -- the use is o

[Python-Dev] Fix for Lib/test/leakers/test_gestalt.py

2006-07-10 Thread Thomas Heller
I think this fixes the leak in Lib/test/leakers/test_gestalt.py. Index: Python/mactoolboxglue.c === --- Python/mactoolboxglue.c (revision 50522) +++ Python/mactoolboxglue.c (working copy) @@ -60,8 +60,9 @@

Re: [Python-Dev] User's complaints

2006-07-10 Thread Armin Rigo
Hi, On Tue, Jul 04, 2006 at 04:49:13PM -0700, Neal Norwitz wrote: > On 7/4/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > > > From actual users of > > the language I get more complaints about the breakneck speed of > > Python's evolution than about the brokenness of the current language. I'

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Matt Fleming
On 10/07/06, Alexander Schremmer <[EMAIL PROTECTED]> wrote: > On Sun, 9 Jul 2006 20:45:05 -0700, Neal Norwitz wrote: > > > There hasn't been much positive response (in the original thread or > > here). Given you forgot about it for over a year, how important can > > it be? :-) > I'm the SoC stude

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

2006-07-10 Thread skip
>> > Part of the reason why its so hard to name this feature is that >> > it's real name is something like "Hey, Python, you know that cool >> > funky thing you do with defining variables in the same scope as >> > they are assigned? Well, don't do that here." Guido> Sorry, th

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Alexander Schremmer
On Sun, 9 Jul 2006 20:45:05 -0700, Neal Norwitz wrote: > There hasn't been much positive response (in the original thread or > here). Given you forgot about it for over a year, how important can > it be? :-) For me it would be very important because I often wonder where the threads are currently

Re: [Python-Dev] "Missing" 2.5 feature

2006-07-10 Thread Scott Dial
Tim Peters wrote: > Just to make life harder ;-), I should note that code, docs and tests > for sys._current_frames() are done, on the tim-current_frames branch. > All tests pass, and there are no leaks in the new code. It's just a > NEWS blurb away from being just another hectic release memory :-

[Python-Dev] TRUNK FREEZE for 2.5b2, tomorrow Tuesday 11th, 00:00 UTC

2006-07-10 Thread Anthony Baxter
The trunk is frozen from 00:00 UTC Tuesday the 11th of July. This is in about 16 hours or so time. As usual, unless you're a member of the release team, please don't checkin past that time until I send an email that the release is done. Thanks, Anthony -- Anthony Baxter <[EMAIL PROTECTED]