At 09:27 PM 6/4/2006 -0400, Jim Jewett wrote:
>Jackilyn is adding logging to several stdlib modules for the Google
>Summer of Code (PEP 337), and asked me to review her first few
>changes.
That PEP doesn't appear to have been approved, and I don't recall any
discussion on Python-Dev. I also coul
Jim> (1) Should we ask Vinay Sajip to add a convenience function (for
Jim> getting the stdlib logger) to the logging module itself?
-1.
Jim> (2) Should NAME be module.__name__?
Seems reasonable.
Jim> (3) Should she put out a message when a (now logged) module is
Jim
Jackilyn is adding logging to several stdlib modules for the Google
Summer of Code (PEP 337), and asked me to review her first few
changes.
There were a few comments that I felt I should double-check with
Python-dev first, in case my own intuition is wrong.
For reference, she is adding the follow
We would like to continue the tradition of having several Python core developers at the Vancouver Python Workshop. This fun conference is small enough to be intimate but consistently attracts top-notch speakers and attendees. We would like YOU (core developer or not) on that list. Although we haven
Collin Winter wrote:
> On 6/4/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> On 6/3/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
>> > Collin Winter wrote:
>> > > Idea: what if Python's -O option caused PySequence_Contains() to
>> > > convert all errors into False return values?
>> >
>> > It woul
On 6/4/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 6/3/06, Georg Brandl <[EMAIL PROTECTED]> wrote:
> > Collin Winter wrote:
> > > Idea: what if Python's -O option caused PySequence_Contains() to
> > > convert all errors into False return values?
> >
> > It would certainly give me an uneasy
The Python Software Foundation's Infrastructure committee has been charged with finding a new tracker system to be used by the Python development team as a replacement for SourceForge. The development team is currently unhappy with SF for several reasons which include:
* Bad interface Most obvi
Tim> Until all this gets resolved, I strongly suggest reverting this
Tim> patch ...
So I won't check in changes to suppress compilation warnings on my Mac.
Andrew, look in your mail for a patch file.
Skip
___
Python-Dev mailing list
Python-De
[Andrew MacIntyre]
> In reviewing the buildbot logs after committing this patch, I see 2
> issues arising that I need advice about...
>
> 1. The Solaris build failure in thread.c has me mystified as I can't
> find any "_sysconf" symbol - is this in a system header?
The patch's
#if THREAD_STACK_M
Paul Jimenez wrote:
> On Friday, Jun 2, 2006, John J Lee writes:
>> [Not sure whether this kind of thing is best posted as tracker comments
>> (but then the tracker gets terribly long and is mailed out every time a
>> change happens) or posted here. Feel free to tell me I'm posting in the
>> wr
On 4-jun-2006, at 15:40, [EMAIL PROTECTED] wrote:
I recall wastemodule.c being mentioned. Now building it is failing
for me (Mac OSX 10.4.6). Was it only wounded but not killed?
Ronald> It that a new failure?
Yes. I svn up and rebuild at least once a week.
The failure was the result
In reviewing the buildbot logs after committing this patch, I see 2
issues arising that I need advice about...
1. The Solaris build failure in thread.c has me mystified as I can't
find any "_sysconf" symbol - is this in a system header?
2. I don't know what to make of the failure of test_thread
>> I recall wastemodule.c being mentioned. Now building it is failing
>> for me (Mac OSX 10.4.6). Was it only wounded but not killed?
Ronald> It that a new failure?
Yes. I svn up and rebuild at least once a week.
Skip
___
Python-Dev mail
On Sun, Jun 04, 2006, Thomas Wouters wrote:
>On 6/4/06, Thomas Wouters <[EMAIL PROTECTED]> wrote:
>>On 6/4/06, Michael Hudson <[EMAIL PROTECTED]> wrote:
>>>
>>> I don't want to pull the 'do you know who I am?' routine, and I know
>>> you're addressing python-dev rather than just me, but I'm current
On 4-jun-2006, at 13:14, [EMAIL PROTECTED] wrote:
I saw a thread here a couple days ago about a bunch of old Mac
cruft going
away. I recall wastemodule.c being mentioned. Now building it is
failing
for me (Mac OSX 10.4.6). Was it only wounded but not killed? The
first
couple of errors
I saw a thread here a couple days ago about a bunch of old Mac cruft going
away. I recall wastemodule.c being mentioned. Now building it is failing
for me (Mac OSX 10.4.6). Was it only wounded but not killed? The first
couple of errors are the key I think:
.../Mac/Modules/waste/wastemodule.c
On 6/4/06, Thomas Wouters <[EMAIL PROTECTED]> wrote:
On 6/4/06, Michael Hudson <
[EMAIL PROTECTED]> wrote:I don't want to pull the 'do you know who I am?' routine, and I know
you're addressing python-dev rather than just me, but I'm currentlysitting in the same room as the guy who wrote py.test :-)
On 6/4/06, Michael Hudson <[EMAIL PROTECTED]> wrote:
"Thomas Wouters" <[EMAIL PROTECTED]> writes:> On 6/4/06, Michael Hudson <[EMAIL PROTECTED]> wrote:> [ For non-checkins readers: Martin Blais checked in un-unittestification
> of test_struct, which spawned questions form Neal and me about whether>
"Thomas Wouters" <[EMAIL PROTECTED]> writes:
> On 6/4/06, Michael Hudson <[EMAIL PROTECTED]> wrote:
> [ For non-checkins readers: Martin Blais checked in un-unittestification
> of test_struct, which spawned questions form Neal and me about whether
> that's really the right thing to do. I also fool
On 6/4/06, Michael Hudson <[EMAIL PROTECTED]> wrote:[ For non-checkins readers: Martin Blais checked in un-unittestification of test_struct, which spawned questions form Neal and me about whether that's really the right thing to do. I also foolishly<
0.5 wink> siggested that, if we switch away from
20 matches
Mail list logo
