On Sat, Oct 2, 2010 at 1:16 PM, Alan McIntyre wrote:
> I have an Intel Core 2 Duo Mac that I was going to convert into a home
> file server in the next couple of weeks, and I'd be glad to set it up
> as a build slave as well. I don't remember what version of OS X it
>
I have an Intel Core 2 Duo Mac that I was going to convert into a home
file server in the next couple of weeks, and I'd be glad to set it up
as a build slave as well. I don't remember what version of OS X it
has on it (it's still packed up in the box), but it certainly won't be
the latest one.
On
On 9/5/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > My build slave (http://www.python.org/dev/buildbot/trunk/x86%20XP%20trunk)
> > keeps failing because of a crash that appears to be in the bsddb
> > module. I assume the master deems the slave to be lost because it's
> > sitting there wait
Hi all,
My build slave (http://www.python.org/dev/buildbot/trunk/x86%20XP%20trunk)
keeps failing because of a crash that appears to be in the bsddb
module. I assume the master deems the slave to be lost because it's
sitting there waiting on me to make a choice on the "debug/abort"
dialog box.
I
Hi all,
There are some new tests for xmlrpclib/SimpleXMLRPCServer that fail
only on the G4 OS X buildbot. Unfortunately, the SimpleXMLRPCServer
returns a vanilla 500 error for any local exceptions, so there's no
obvious (to me) way to find out what's going wrong without having a G4
Mac on hand (w
On 8/4/07, Jeffrey Yasskin <[EMAIL PROTECTED]> wrote:
> Well, regardless of the brokenness of the patch, I do get two
> different failures from this test on OSX. The first is caused by
> trying to socket.bind() a port that's already been bound recently:
> That looks pretty easy to fix.
It was fix
Hasan,
We made a change to bind the server to port 0, so that an unused port
is selected for each test. I wasn't able to reproduce the failure
after making this change; is the current trunk still failing for you?
Cheers,
Alan
On 7/30/07, Hasan Diwan <[EMAIL PROTECTED]> wrote:
> The issue seems
Thanks Hasan, I'll see if I can dig up what they did and make some
changes to fix the asyncore tests.
Regards,
Alan
On 7/26/07, Hasan Diwan <[EMAIL PROTECTED]> wrote:
> test_asyncore fails intermittently on Darwin in trunk rev 56558; it
> seems a matter of executing the test too fast and not wait
On 5/23/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Tim Peter's machine comes and goes, depending on whether he starts
> the buildbot. Alan McIntyre's machien should be mostly he reliable,
> but nobody really notices if it goes away.
FWIW, my current internet service is less than spectacula
Hi all,
Bug #1717900 has an example of a script that causes a (cryptic, IMO)
error during module cleanup since instances of a class just happen to
get destroyed after their class is destroyed, and the __del__ method
manipulates a class attribute. As I understand it this is expected
under the beha
I posted what I hope can be the final update to patch 1121142 (adding
an open() method to ZipFile that returns a read-only file-like
object). If anybody has time to review and apply it I would appreciate
it.
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1121142&group_id=5470
If I f
On 2/17/07, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> I ran into the same thing and made a patch a long while ago (the one
> Martin mentioned):
>
> https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1121142&group_id=5470
>
> I am actually working
On 2/16/07, Derek Shockey <[EMAIL PROTECTED]> wrote:
> Since I was writing a script to work with potentially very large zipped
> files, I took it upon myself to write an extract() method for zipfile, which
> is essentially an adaption of the read() method modeled after tarfile's
> extract(). I feel
The "x86 XP trunk" build slave will be down for a bit longer,
unfortunately. Tropical storm Ernesto got in the way of my DSL
installation - I don't have a new install date yet, but I'm assuming
it's going to be Tuesday or later.
Alan
___
Python-Dev mail
Hi all,
The Windows build slave ("x86 XP trunk") will be down for most of
today while I move to a new apartment. As long as the phone company
manages to provide me with an internet connection by the end of today,
it should be available again some time this evening.
Alan
_
A.M. Kuchling wrote:
> On Tue, Apr 25, 2006 at 06:04:12PM -0400, Jim Jewett wrote:
>
>> So how are the committers supposed to even know that it is waiting for
>> assessment? The solutions that I've seen work are
>>
>
> Could we mark the bug/patch as status 'pending'? This status exists
>
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
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
e frame, but I wanted to
set a realistically achievable minimum for the proposal. If anybody can
offer helpful feedback on a good minimum number I'd appreciate it.
Not-guru-ish-enough-to-found-a-new-web-framework'ly yours,
Alan McIntyre
___
Python
The current PCBuild/readme.txt directs people to
http://sources.redhat.com/bzip2 to get the 1.0.2 version of libbz2. The
RedHat link redirects to http://www.bzip.org, which shows that 1.0.3 was
released in February 2005. I suggest that Python 2.5 should move up to
1.0.3, and that readme.txt shoul
Brett Cannon wrote:
>And Tim had a good point about PDAs and such; how are they supposed to
>exit? What if someone picked up Python for their Nokia S60 phone and
>tried to exit from the interpreter? Unless Nokia has tweaked
>something I don't know how they would know to exit without knowing
>abo
Fredrik Lundh wrote:
>does a plain
>
>a = -100.0
>
>still work on your machine?
>
D'oh - I seriously broke something, then, because it didn't.
funny_falcon commented on the patch in SF and suggested a change that
took care of that. I've uploaded the corrected version of the patch,
wh
Tim Peters wrote:
>[Adam Olsen]
>
>>https://sourceforge.net/tracker/index.php?func=detail&aid=1334979&group_id=5470&atid=305470>
>>
>>That patch removes the division from the loop (and fixes the bugs),
>>but gives only a small increase in speed.
>>
>In any case, I agree it _should_ fix the bugs (a
Bob Ippolito wrote:
> One of the most useful things that could happen to the zipfile module
> would be a stream interface for both reading and writing. Right now
> it's slow and memory hungry when dealing with large chunks. The use
> case that lead me to fix this bug is a tool that archives vide
Johannes Gijsbers wrote:
On Sun, Feb 27, 2005 at 03:45:37PM -0500, Alan McIntyre wrote:
Martin,
Thanks; that works very well (in Firefox, too). I got it to work
for patches, but the URL is a bit uglier (like this:
http://sourceforge.net/tracker/index.php?func=detail&aid=$&group_id=5
Martin,
Thanks; that works very well (in Firefox, too). I got it to work for
patches, but the URL is a bit uglier (like this:
http://sourceforge.net/tracker/index.php?func=detail&aid=$&group_id=5470&atid=305470).
I assume there's a way to shorten that some, but it works as is and I
probably won
I've taken a look at the following patches and made comments on the
associated tracker items:
patch [977553] Speed up EnumKey call
Looks like a good idea, but needs some cleanup and at least one
test case. I think I know enough about the Windows registry functions
to finish this one up
27 matches
Mail list logo
