Brett Cannon wrote:
> here is the rough draft of the PEP for packages maintained externally
> from Python itself. There is some missing, though, that I would like
> help filling in.
>
> I don't know who to list as the contact person (i.e., the Python
> developer in charge of the code) for Expat,
I'm not convinced.
On 4/25/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 11:29 PM 4/25/2006 -0400, Phillip J. Eby wrote:
> >See, if @contextfactory functions return a thing *with* a __context__
> >method, how is that usable with "with"? It isn't, unless the thing also
> >happens to have __en
Something's gone south in the GNU info conversion of the documentation on the
trunk. If there's anyone here with time to look at it, I'd appreciate it.
Unfortunately, the GNU info conversion is one of the bits I understand the
least in the doc tool chain, and there's little information in the
At 11:29 PM 4/25/2006 -0400, Phillip J. Eby wrote:
>See, if @contextfactory functions return a thing *with* a __context__
>method, how is that usable with "with"? It isn't, unless the thing also
>happens to have __enter__/__exit__ methods. This was the hole in the
>documentation that caused Nick
At 08:09 PM 4/25/2006 -0700, Guido van Rossum wrote:
>On 4/25/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> > At 05:20 PM 4/25/2006 -0700, Guido van Rossum wrote:
> > >I would augment #1 to clarify that if you have __enter__ and __exit__
> > >you may not have __context__ at all; if you have all t
On 4/25/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 05:20 PM 4/25/2006 -0700, Guido van Rossum wrote:
> >I would augment #1 to clarify that if you have __enter__ and __exit__
> >you may not have __context__ at all; if you have all three,
> >__context__ must return self.
>
> Well, requiring t
On 4/2/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Tim Peters wrote:
> > For gcc we _could_ solve it in the obvious way, which I guess Martin
> > was hoping to avoid: change Unixish config to detect whether the
> > platform C supports the "z" format modifier (I believe gcc does), and
> > if
here is the rough draft of the PEP for packages maintained externally
from Python itself. There is some missing, though, that I would like
help filling in.
I don't know who to list as the contact person (i.e., the Python
developer in charge of the code) for Expat, Optik or pysqlite. I know
Greg
"Terry Reedy" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> The most useful thing I can think of is to be able to tag each item by
> the doc section (lang ref, lib ref, tut, pep) most applicable to the item
> and then be able to sort tracker items (on any of the lists, possibly)
At 04:41 PM 4/25/2006 -0700, Brent Fulgham wrote:
>"Included are summary descriptions of the formats of all of the standard
>metadata produced by setuptools, along with pointers to the existing
>manuals that describe the syntax used for representing requirements, entry
>points, etc. as text. The .
At 05:20 PM 4/25/2006 -0700, Guido van Rossum wrote:
>I would augment #1 to clarify that if you have __enter__ and __exit__
>you may not have __context__ at all; if you have all three,
>__context__ must return self.
Well, requiring the __context__ allows us to ditch the otherwise complex
problem
On 4/25/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 04:18 PM 4/25/2006 -0700, Guido van Rossum wrote:
> >But the question remains,
> >under what circumstances is it convenient to call __context__()
> >explicit, and pass the result to a with-statement?
>
> Oh. I don't know of any; I previous
At 04:31 PM 4/25/2006 -0700, Aahz wrote:
>Right -- I've already been chastised for that. Unless someone has a
>better idea, I'm going to call it a "wrapper".
Better idea: just delete the parenthetical about a namespace and leave the
rest of your text alone, at least until the dust settles. I th
At 04:18 PM 4/25/2006 -0700, Guido van Rossum wrote:
>But the question remains,
>under what circumstances is it convenient to call __context__()
>explicit, and pass the result to a with-statement?
Oh. I don't know of any; I previously asked the same question myself. I
just eventually answered m
"Included are summary descriptions of the formats of all of the standard
metadata produced by setuptools, along with pointers to the existing
manuals that describe the syntax used for representing requirements, entry
points, etc. as text. The .egg, .egg-info, and .egg-link formats and
layouts
On Tue, Apr 25, 2006, Guido van Rossum wrote:
> On 4/24/06, Aahz <[EMAIL PROTECTED]> wrote:
>>
>> Let's go back to a pseudo-coded with statement:
>>
>> with EXPRESSION [as NAME]:
>> BLOCK
>>
>> What happens while BLOCK is being executed? Again, here's what I said
>> originally:
>>
>>
"Jim Jewett" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>> The latest weekly tracker summary says about 1300, + 200 RFEs. ...
>
>> I worry about ... a batch of 50-100 nice new patches could then sit
>> unreviewed on the patch tracker along with those already there.
>
> Is there
On 4/24/06, Aahz <[EMAIL PROTECTED]> wrote:
> Let's go back to a pseudo-coded with statement:
>
> with EXPRESSION [as NAME]:
> BLOCK
>
> What happens while BLOCK is being executed? Again, here's what I said
> originally:
>
> EXPRESSION returns a value that the with statement uses t
"Brett Cannon" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> So, if you could, please reply to this message with ONE thing you have
> found in a tracker other than SF that you have liked (especially
> compared to SF) and ONE thing you dislike/hate about SF's tracker. I
> will use
On 4/25/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 11:37 AM 4/25/2006 -0700, Guido van Rossum wrote:
> >But what's the use case? Have we actually got an example where it
> >makes sense to use the "thing with __enter__ and __exit__ methods" in
> >a with-statement, other than the (many) examp
Nick Coghlan wrote:
> (An idea that just occurred to me in writing this email is "managed
> context". That's a lot less clumsy, and fits with the context manager
> idea.
+1
> Context expressions
> In response to a comment Aahz made, I tweaked the language
> reference to explicitly refer to the
Please see
http://svn.python.org/projects/sandbox/trunk/setuptools/doc/formats.txt for
source, or http://peak.telecommunity.com/DevCenter/EggFormats for an
HTML-formatted version.
Included are summary descriptions of the formats of all of the standard
metadata produced by setuptools, along wit
On Mon, Apr 24, 2006 at 08:31:19AM +0200, "Martin v. L?wis" wrote:
>Sean Reifschneider wrote:
>> Thoughts?
>
>In Python 2.5, exit(0) exits.
Eeexcellent.
Thanks,
Sean
--
UNIX was not designed to stop you from doing stupid things, because that
would also stop you from doing clever things. -- Do
> If there are too many patches waiting for a committer to assess them,
> that probably points up the need for more committers.
Perhaps; part of the problem is with the SF workflow.
New bug or patch comes in. Shows up on the list of new bugs, but not
obviously ready for action. Not assigned to
> So things like decimal.Context get left trying to find a sane
> name for what their __context__ method returns.
> decimal.Context.__context__() returns a . . . context? What?
> Wasn't it already a context? Oh, so it actually returns a
> "with statement context object".
[I was OK with "context sp
On Tue, Apr 25, 2006 at 04:10:02PM -0400, Jim Jewett wrote:
> I don't see a good way to say "It looks good to me". I don't see any
> way to say "There were issues, but I think they're resolved now". So
> either way, I and the author are both sort of waiting for a committer
> to randomly happen ba
I am starting to hash out what the Call for Trackers is going to say
on the Infrastructure mailing list. Laura Creighton suggested we have
a list of features that we would like to see and what we all hate
about SF so as to provide some guidelines in terms of how to set up
the test trackers that pe
> The latest weekly tracker summary says about 1300, + 200 RFEs. ...
> I worry about ... a batch of 50-100 nice new patches could then sit
> unreviewed on the patch tracker along with those already there.
Is there a good way to flag a patch as reviewed and recommendation made?
I understand that
At 11:37 AM 4/25/2006 -0700, Guido van Rossum wrote:
>But what's the use case? Have we actually got an example where it
>makes sense to use the "thing with __enter__ and __exit__ methods" in
>a with-statement, other than the (many) examples where the original
>__context__ method returns "self"?
Ob
But what's the use case? Have we actually got an example where it
makes sense to use the "thing with __enter__ and __exit__ methods" in
a with-statement, other than the (many) examples where the original
__context__ method returns "self"?
--Guido
On 4/24/06, Nick Coghlan <[EMAIL PROTECTED]> wrote
"A.M. Kuchling" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Mon, Apr 24, 2006 at 09:45:41PM -0700, Neal Norwitz wrote:
>> hard bugs to fix. I guess there are also a lot that we can't
>> reproduce and the submitter is MIA. Those might be easier. Ping them
>> if not reproduc
"Alan McIntyre" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I suppose the "new code" emphasis may make writing a proposal to fix
> bugs an exercise in futility. :)
I personally consider anything *you* write to be 'new code'. Let us see
what Google thinks. Patches that other
At 12:08 AM 4/26/2006 +1000, Nick Coghlan wrote:
>Secondly, the documentation now shows an example
>of a class with a close() method using contextlib.closing directly as its own
>__context__() method.
Sadly, that would only work if closing() were a function. Classes don't
get turned into methods
On Tue, 25 Apr 2006, A.M. Kuchling wrote:
> On Mon, Apr 24, 2006 at 09:45:41PM -0700, Neal Norwitz wrote:
>> hard bugs to fix. I guess there are also a lot that we can't
>> reproduce and the submitter is MIA. Those might be easier. Ping them
>> if not reproducible, if no response in a month, we
On Wed, Apr 26, 2006 at 12:08:47AM +1000, Nick Coghlan wrote:
> However, I made the
> changes below in order to address the conflicts between the alpha 1
> documentation and implementation.
IMHO this set of changes makes the terminology reasonably clear, so
I'm happy with it. I've edited the Wh
A.M. Kuchling wrote:
> On Mon, Apr 24, 2006 at 12:30:12PM -0400, Alan McIntyre wrote:
>
>> My unglamorous proposal is to review bugs & patches (starting with the
>> oldest) and resolve at least 200 of them. Is that too much? Too few?
>>
> I'd suggest 75 or maybe 100 bugs or patches, not
Phillip J. Eby wrote:
> If qualification of "context" is the only problem, I propose:
>
> context manager -- thing with __context__ method
> execution context object -- thing with __enter__/__exit__/__context__
> execution context -- the abstract thing set up and torn down by the ECO
>
> "When re
Terry Reedy wrote:
>> My unglamorous proposal is to review bugs & patches (starting with the
>> oldest) and resolve at least 200 of them.
> Funny, and nice!, that you should propose this. I thought of adding
> something like this to the Python wiki as something I might mentor, but
> hesitate
I won't call this a resolution yet, since it'll probably be a few days before
I get time to update the PEP itself, and the changes below are based on
pulling together a few different threads of the recent discussion. However, I
believe (hope?) we're very close to being done :)
The heart of the
At 07:24 PM 4/25/2006 +1000, Nick Coghlan wrote:
>So things like decimal.Context get left trying to find a sane name for what
>their __context__ method returns. decimal.Context.__context__() returns a . .
>. context? What? Wasn't it already a context? Oh, so it actually returns a
>"with statement c
Hi all,
A shameless plug and reminder for EuroPython 2006 (July 3-5):
* you can submit talk proposals until May 31st.
* there is a refereed papers track; deadline for abstracts: May 5th.
See the full call for papers below.
A bientot,
Armin Rigo & Carl Friedrich Bolz
==
"Neil Hodgson" <[EMAIL PROTECTED]> writes:
> Martin v. Löwis:
>
>> Apparently, the status of this changed right now: it seems that
>> the 2003 compiler is not available anymore; the page now says
>> that it was replaced with the 2005 compiler.
>>
>> Should we reconsider?
>
>I expect Microsoft
On Mon, Apr 24, 2006 at 09:45:41PM -0700, Neal Norwitz wrote:
> hard bugs to fix. I guess there are also a lot that we can't
> reproduce and the submitter is MIA. Those might be easier. Ping them
> if not reproducible, if no response in a month, we close.
The last time there was a thread sugges
Paul Moore wrote:
> On 4/25/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> I still found the alpha 1 terminology and documentation completely
> natural and intuitive. Completely. Not "acceptable", but "completely
> natural". From the perspective of someone with limited understanding
> of the design,
On 4/25/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> PEP 343 made a *deliberate, conscious design decision* to copy the semantics
> of iterators by making the context management protocol a superset of the
> context protocol (or rather, the context specification protocol in alpha 2).
OK. It's poss
On Tuesday 25 April à 01:24, "Martin v. Löwis" wrote:
> Sylvain Thénault wrote:
> > I've posted a patch (#1475523) for this and assigned it to Martin Von
> > Loewis since he was the core developper who has made some followup on
> > the original bug. Could someone (Martin or someone else) quick re
46 matches
Mail list logo
