Hi,
I modified regrtest to not ignore -j1 anymore (issue #25285). I also
modified Tools/buildbot/test.bat to add the -j1 option (-j1 was
already used on UNIX on "make buildbottest").
All buildbots will now run each test file in a fresh subprocess. It
helps to restrict all kinds of side effects of
Éric Araujo wrote:
> Do we have buildbots with the rpm programs installed? There is a patch
> I want to commit to fix a bug in distutils’ bdist_rpm; it was tested by
> the patch author, but I cannot verify it on my machine, so I would feel
> safer if our buildbot fleet would cover that.
Yes, the
Hi,
Do we have buildbots with the rpm programs installed? There is a patch
I want to commit to fix a bug in distutils’ bdist_rpm; it was tested by
the patch author, but I cannot verify it on my machine, so I would feel
safer if our buildbot fleet would cover that.
Thanks
Victor Stinner writes:
> But today I saw a a buildbot timeout without any traceback: a possible hang
> in
> test_io on "x86 FreeBSD 7.2 3.x" buildbot, "command timed out: 3900 seconds
> without output". I realized that some buildbots (all buildbots?) override the
> TESTOPTS variable ("make bu
On 6 June 2011 11:29, Victor Stinner wrote:
> Stephan Krah asked me to change how the default timeout is defined for
> regrtest
> (issue #12250):
>
> "The implicit timeout in regrtest.py makes it harder to write automated
> test scripts for 3rd party modules. First, you have to remember to
> set
Hi,
Stephan Krah asked me to change how the default timeout is defined for regrtest
(issue #12250):
"The implicit timeout in regrtest.py makes it harder to write automated
test scripts for 3rd party modules. First, you have to remember to
set --timeout=0 for long running tests. Then, you have to
On 4/20/2011 7:57 AM, Ethan Furman wrote:
Victor Stinner wrote:
Finally, I'm very happy to see that my faulthandler module was as useful
as I expected [...]
Congratulations! Nice work.
Ditto. Multiple pats on the back.
--
Terry Jan Reedy
___
Pyth
Victor Stinner wrote:
Finally, I'm very happy to see that my faulthandler module was as useful
as I expected [...]
Congratulations! Nice work.
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-d
On Wed, Apr 20, 2011 at 7:37 PM, Victor Stinner
wrote:
> Finally, I'm very happy to see that my faulthandler module was as useful
> as I expected: with more informations, we are now able to identify race
> conditions. I hope that we will fix all remaining threading, signal and
> subprocess race co
Hi,
The new faulthandler module is now fully functional and it has no more
known issue. Its timeout feature is used on regrtest to dump the Python
backtrace and exit if a test takes more than 1 hour.
Using the regrtest timeout and faulthandler signal handlers (enable in
regrtest), I started to co
On Fri, 25 Mar 2011 16:11:16 +0100
Éric Araujo wrote:
> Le 25/03/2011 15:58, Stefan Krah a écrit :
> > Incidentally, I noticed that push messages with an issue number get
> > redirected to bugs.python.org. See the recent commit for #2650 here:
> >
> > http://hg.python.org/cpython/
> >
> >
> >
Le 25/03/2011 15:58, Stefan Krah a écrit :
> Incidentally, I noticed that push messages with an issue number get
> redirected to bugs.python.org. See the recent commit for #2650 here:
>
> http://hg.python.org/cpython/
>
>
> Is this really what everyone wants?
Having issues linked from commit m
Antoine Pitrou wrote:
> > I'm unable to figure out how to trigger a build of a feature branch, see:
>
> You cannot do that yet.
Ok, thanks.
Incidentally, I noticed that push messages with an issue number get
redirected to bugs.python.org. See the recent commit for #2650 here:
http://hg.python
On Fri, 25 Mar 2011 15:30:37 +0100
Stefan Krah wrote:
> Hi,
>
> I'm unable to figure out how to trigger a build of a feature branch, see:
You cannot do that yet.
Regards
Antoine.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.
Hi,
I'm unable to figure out how to trigger a build of a feature branch, see:
http://www.python.org/dev/buildbot/all/builders/x86%20Ubuntu%20Shared%203.x/builds/3424
I saw this:
'Branch to build' is relative to http://svn.python.org/projects/python.
But if I leave out the branch, nothing ha
Mark Dickinson wrote:
> On Fri, Apr 2, 2010 at 3:54 PM, Stefan Krah wrote:
> >
> > I looks like the 'stop build' button can a) cause subsequent builds to fail
> > and b) cause pending builds to be deleted from the queue.
> >
> >
> > a) http://www.python.org/dev/buildbot/builders/ARM Linux EABI 3.
On Fri, Apr 2, 2010 at 3:54 PM, Stefan Krah wrote:
>
> I looks like the 'stop build' button can a) cause subsequent builds to fail
> and b) cause pending builds to be deleted from the queue.
>
>
> a) http://www.python.org/dev/buildbot/builders/ARM Linux EABI 3.x/builds/18
> was apparently interr
Hi,
I looks like the 'stop build' button can a) cause subsequent builds to fail
and b) cause pending builds to be deleted from the queue.
a) http://www.python.org/dev/buildbot/builders/ARM Linux EABI 3.x/builds/18
was apparently interrupted by a 'stop build' for a previous build.
b) I stop
Hello,
I realize I may have missed some kind of formal announcement, but why
have all the buildbots been down for a number of days (weeks?) now?
Thanks
Antoine.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinf
Martin v. Löwis wrote:
Looking at http://www.python.org/dev/buildbot/, we are still missing buildbots
for the release26-maint and release30-maint branches. Is someone working on
that?
Yes. I won't enable 2.6 build slaves until 2.5.3 is released, but will
afterwards.
How does one actually dow
> Looking at http://www.python.org/dev/buildbot/, we are still missing buildbots
> for the release26-maint and release30-maint branches. Is someone working on
> that?
Yes. I won't enable 2.6 build slaves until 2.5.3 is released, but will
afterwards.
Regards,
Martin
__
Hello,
On Sun, Dec 7, 2008 at 00:19, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> BTW, 3.0 went out the door with test_binascii failing on windows.
> Was surprised that some buildbot wasn't complaining.
They were complaining. But not loud enough to stop the release.
(see bottom of
http://www.py
BTW, 3.0 went out the door with test_binascii failing on windows.
Was surprised that some buildbot wasn't complaining.
- Original Message -
From: "Antoine Pitrou" <[EMAIL PROTECTED]>
To:
Sent: Saturday, December 06, 2008 3:15 PM
Subject: [Python-Dev] Buil
Hello people,
Looking at http://www.python.org/dev/buildbot/, we are still missing buildbots
for the release26-maint and release30-maint branches. Is someone working on
that?
Regards
Antoine.
___
Python-Dev mailing list
Python-Dev@python.org
http
Benjamin Peterson wrote:
> On Thu, Oct 30, 2008 at 3:38 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>>> AFAICS there are no buildbots for the release26-maint branch.
>> That's correct. I'm waiting to create them until after we retire the
>> 2.5 ones.
>
> That reminds me: Do we have a final re
On Thu, Oct 30, 2008 at 3:38 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> AFAICS there are no buildbots for the release26-maint branch.
>
> That's correct. I'm waiting to create them until after we retire the
> 2.5 ones.
That reminds me: Do we have a final release date for 2.5.3 set?
--
> AFAICS there are no buildbots for the release26-maint branch.
That's correct. I'm waiting to create them until after we retire the
2.5 ones.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/pyth
AFAICS there are no buildbots for the release26-maint branch.
Thomas
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-arch
Hi and thanks for your answers,
> If you are able to offer something that's not on the list, that'd be
> good. But any help at all is appreciated.
>
> I believe Windows has traditionally been under-represented in all
> buildbot farms, and it's likely to stay that way...
Well what I could provide
On Mon, Jul 7, 2008 at 5:39 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
>
>
> - are more buildbots needed and if so, which kinds of platforms/architectures?
I can't really answer that question for the python code buildbot farm,
but for the Pybots community project, the platforms we currently hav
Hello,
As someone who could (perhaps) (potentially) provide a buildbot machine, there
are several questions which need answering before I take a decision:
- are more buildbots needed and if so, which kinds of platforms/architectures?
- for which software? Python itself? third-party apps and libr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 12, 2008, at 9:47 AM, Alexandre Vassalotti wrote:
On Mon, May 12, 2008 at 9:24 AM, "Martin v. Löwis"
<[EMAIL PROTECTED]> wrote:
The idea was to replace the orignial module file with its stub.
However, the "svn copy" and edit process isn't t
> Hmm, that's interesting information. I suspect I could easily create
> more bugs than I solve by using it, but it's interesting to know
> nevertheless.
I've been trying to use for a few applications. The biggest short-coming
is that it won't work for all cases. In particular, for the following
o
2008/5/12 "Martin v. Löwis" <[EMAIL PROTECTED]>:
> > 1.0. There are still case folding bugs in 1.0 - I'm working on fixing
> > them. But there will never be a complete fix for this situation, as
> > it's simply not possible to checkout the exact svn layout of that
> > revision on a case-folding
> 1.0. There are still case folding bugs in 1.0 - I'm working on fixing
> them. But there will never be a complete fix for this situation, as
> it's simply not possible to checkout the exact svn layout of that
> revision on a case-folding system, it simply can't be supported
> (without name manglin
> Hmm, Guido's been at the time machine again :-)
>
>> svn log http://svn.python.org/projects/python/trunk | tail
>
> r2161 | guido | 1990-08-09 15:25:15 +0100 (Thu, 09 Aug 1990) | 2 lines
>
> Initial revision
>
> -
2008/5/12 Paul Moore <[EMAIL PROTECTED]>:
> 2008/5/12 "Martin v. Löwis" <[EMAIL PROTECTED]>:
> > Subversion's first release was in October 2000; it wasn't self-hosting
> > until 2001 :-)
>
> I assume it's pre-svn history, converted from CVS. Or I'm misreading
> something. Whatever, it's from
2008/5/12 Alexandre Vassalotti <[EMAIL PROTECTED]>:
> Which version of mercurial are you using? I know that versions prior
> 1.0 had some bug with handling case-changes on case-insensitive
> filesystems.
1.0. There are still case folding bugs in 1.0 - I'm working on fixing
them. But there will
2008/5/12 "Martin v. Löwis" <[EMAIL PROTECTED]>:
> > Revision 63129 is not valid on case folding filesystems. In
> > particular, this horribly breaks using hg-svn to make a local mirror
> > of the Python repository:
>
> That would be a bug in hg-svn, right? Yes, the revision is not valid
> on c
On Mon, May 12, 2008 at 9:24 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > The idea was to replace the orignial module file with its stub.
> > However, the "svn copy" and edit process isn't the cause of the
> > problems. It is the fact that 2 files existed in the same directory
> > differ
> The idea was to replace the orignial module file with its stub.
> However, the "svn copy" and edit process isn't the cause of the
> problems. It is the fact that 2 files existed in the same directory
> differing only by a case-change.
I still don't understand. You wanted to replace the file with
On Mon, May 12, 2008 at 7:18 AM, Paul Moore <[EMAIL PROTECTED]> wrote:
> Revision 63129 is not valid on case folding filesystems. In
> particular, this horribly breaks using hg-svn to make a local mirror
> of the Python repository:
>
> >\Apps\HGsvn\hgimportsvn.exe -r 63120
> http://svn.python.
On Mon, May 12, 2008 at 3:49 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Well, I guess I really messed up on that one. So, do you have any idea
> > on how to revert the changes?
>
> If the changes where in a single revision N, do
>
> svn merge -rN:N-1 .
> svn commit -m "revert rN"
>
>
On Mon, May 12, 2008 at 3:40 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > When I rename a module I use "svn copy", since "svn remove" doesn't
> > pick up changes made to the "deleted" file. For example, here is what
> > I did for PixMapWrapper:
>
> You want to make changes to the deleted
> Revision 63129 is not valid on case folding filesystems. In
> particular, this horribly breaks using hg-svn to make a local mirror
> of the Python repository:
That would be a bug in hg-svn, right? Yes, the revision is not valid
on case-folding systems - but why should that break hg-svn? The tool
2008/5/12 Paul Moore <[EMAIL PROTECTED]>:
> Bazaar seems to be OK (ish) with this - it picks just one version to show.
It seems to be unable to find the history using either bzr log
Lib\socketserver.py or bzr log Lib\SocketServer.py, though (but bzr
log seems pretty unintuitive to me, so maybe I
2008/5/12 Alexandre Vassalotti <[EMAIL PROTECTED]>:
> On Sun, May 11, 2008 at 5:29 PM, Alexandre Vassalotti
> <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > I have been working the module renaming for PEP-3108, and I just
> > noticed that some buildbots are throwing errors while updating their
> Well, I guess I really messed up on that one. So, do you have any idea
> on how to revert the changes?
If the changes where in a single revision N, do
svn merge -rN:N-1 .
svn commit -m "revert rN"
If they span over several subsequent revisions, use N-k
instead. If they span over several revisi
> When I rename a module I use "svn copy", since "svn remove" doesn't
> pick up changes made to the "deleted" file. For example, here is what
> I did for PixMapWrapper:
You want to make changes to the deleted file? Why?
Regards,
Martin
___
Python-Dev ma
On Sun, May 11, 2008 at 5:29 PM, Alexandre Vassalotti
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have been working the module renaming for PEP-3108, and I just
> noticed that some buildbots are throwing errors while updating their
> checkout. It seems the method I use for renaming modules hits a
> s
On Sun, May 11, 2008 at 3:38 PM, Alexandre Vassalotti
<[EMAIL PROTECTED]> wrote:
> On Sun, May 11, 2008 at 6:31 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> The PEP specifies the lib-old directory to hold the old case name so
>> that the svn rename won't lead to two files in the same directory. I
On Sun, May 11, 2008 at 6:31 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> The PEP specifies the lib-old directory to hold the old case name so
> that the svn rename won't lead to two files in the same directory. I
> was hoping that creating the stub in lib-old would allow a simple
> ``svn rename``
On Sun, May 11, 2008 at 3:16 PM, Alexandre Vassalotti
<[EMAIL PROTECTED]> wrote:
> On Sun, May 11, 2008 at 5:44 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
>> 2008/5/11 Alexandre Vassalotti <[EMAIL PROTECTED]>:
>>> When I rename a module I use "svn copy", since "svn remove" doesn't
>>> pick up change
On Sun, May 11, 2008 at 5:44 PM, Paul Moore <[EMAIL PROTECTED]> wrote:
> 2008/5/11 Alexandre Vassalotti <[EMAIL PROTECTED]>:
>> When I rename a module I use "svn copy", since "svn remove" doesn't
>> pick up changes made to the "deleted" file. For example, here is what
>> I did for PixMapWrapper:
>>
On Sun, May 11, 2008 at 11:45:03PM +0200, Georg Brandl wrote:
> In any case, how does SVN on Windows handle this situation, having two
> identical filenames -- except for case -- in one directory?
Very bad. It's completely confused. It can checkout one of the files and
commit the other.
Oleg.
Alexandre Vassalotti schrieb:
When I rename a module I use "svn copy", since "svn remove" doesn't
pick up changes made to the "deleted" file. For example, here is what
I did for PixMapWrapper:
svn copy ./Lib/plat-mac/PixMapWrapper.py ./Lib/plat-mac/pixmapwrapper.py
edit ./Lib/plat-mac/Pix
Sorry, should have gone to the list:
2008/5/11 Alexandre Vassalotti <[EMAIL PROTECTED]>:
> When I rename a module I use "svn copy", since "svn remove" doesn't
> pick up changes made to the "deleted" file. For example, here is what
> I did for PixMapWrapper:
>
> svn copy ./Lib/plat-mac/PixMapWra
Hello,
I have been working the module renaming for PEP-3108, and I just
noticed that some buildbots are throwing errors while updating their
checkout. It seems the method I use for renaming modules hits a
subversion bug on certain platforms. The error thrown looks like this:
...
svn: In directory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Heimes wrote:
| More than 5 years ago Zope Corp was working on a Berkeley DB backend for
| ZODB. It was more of a marketing decision to show large companies that
| ZODB is using a well known database instead of a self made one. The
| project
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guido van Rossum wrote:
| Correction: the subversion BerkeleyDB backend is still very much alive
| and kicking. There were some early issues (they did things that
| SleepyCat told them not to do :-) but it was corrected and it's still
| working fine fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Heimes wrote:
| Oh yeah ... ZODB4 and BDBStorage ... a dark chapter starting with high
| hopes and ending in tragedy ... Several projects like Zope and
| Subversion worked hard on a a Berkeley DB backend but in the end all
| projects had the
Oleg Broytmann wrote:
>Sorry, can I ask an additional question? These words - what they were
> about? about the architecture of BDBStorage and Subversion, or about the
> very BerkeleyDB, or about what?
I don't know all details and it was several years ago so some of my
saying may not be correc
Correction: the subversion BerkeleyDB backend is still very much alive
and kicking. There were some early issues (they did things that
SleepyCat told them not to do :-) but it was corrected and it's still
working fine for several large users.
On Thu, Feb 28, 2008 at 12:00 PM, Christian Heimes <[EM
Guido van Rossum wrote:
> This was the fault of the svn developers, not of BerkeleyDB. And svn
> has fixed the issues.
I got that in your last mail ;)
Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/p
On Thu, Feb 28, 2008 at 12:23 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > Correction: the subversion BerkeleyDB backend is still very much alive
> > and kicking. There were some early issues (they did things that
> > SleepyCat told them not to do :-) but it was
Guido van Rossum wrote:
> Correction: the subversion BerkeleyDB backend is still very much alive
> and kicking. There were some early issues (they did things that
> SleepyCat told them not to do :-) but it was corrected and it's still
> working fine for several large users.
Thanks for the correcti
On Thu, Feb 28, 2008 at 09:00:54PM +0100, Christian Heimes wrote:
> Oh yeah ... ZODB4 and BDBStorage ... a dark chapter starting with high
> hopes and ending in tragedy ... Several projects like Zope and
> Subversion worked hard on a a Berkeley DB backend but in the end all
> projects had the same
Fred Drake wrote:
> The BDBStorage is long gone at this point. Few are so unfortunate as
> to remember it (though a few who may just might be on this list). :-)
Oh yeah ... ZODB4 and BDBStorage ... a dark chapter starting with high
hopes and ending in tragedy ... Several projects like Zope and
On Feb 27, 2008, at 10:45 PM, Fred Drake wrote:
> On Feb 27, 2008, at 9:13 AM, A.M. Kuchling wrote:
>> Doing a code search finds a fair number of users of the module:
>> Zope's
>> BDBStorage, ...
>
> The BDBStorage is long gone at this point. Few are so unfortunate as
> to remember it (though a
On Feb 27, 2008, at 9:13 AM, A.M. Kuchling wrote:
> Doing a code search finds a fair number of users of the module: Zope's
> BDBStorage, ...
The BDBStorage is long gone at this point. Few are so unfortunate as
to remember it (though a few who may just might be on this list). :-)
-Fred
-
> Maybe the flaky tests could be moved towards the end? This way we could
> at least see if the other tests work.
It's intentional that the tests run in a random order.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pytho
Neal Norwitz schrieb:
> On Tue, Feb 26, 2008 at 11:47 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>>
>> Well, in my opinion "batteries included" is great, but not when one of
>> the batteries consistently acts up and requires a good shake to get
>> working again. The bsddb module has consistent
On Tue, Feb 26, 2008 at 11:47 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> Well, in my opinion "batteries included" is great, but not when one of
> the batteries consistently acts up and requires a good shake to get
> working again. The bsddb module has consistent reliability issues when
> i
On Tue, Feb 26, 2008 at 09:46:04PM -0800, Gregory P. Smith wrote:
> My opinion on bsddb as a standard library module is based mostly on "its
> always been there" and a vague memory of the last time this came up I
> thought people piped up saying they liked batteries being included,
> including bsdd
On Tue, Feb 26, 2008 at 9:46 PM, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
>
>
>
> On 2/26/08, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > On Tue, Feb 26, 2008 at 1:52 PM, Facundo Batista
> > <[EMAIL PROTECTED]> wrote:
> > > 2008/2/26, "Martin v. Löwis" <[EMAIL PROTECTED]>:
> > >
> > >
> > > > T
On 2/26/08, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> On Tue, Feb 26, 2008 at 1:52 PM, Facundo Batista
> <[EMAIL PROTECTED]> wrote:
> > 2008/2/26, "Martin v. Löwis" <[EMAIL PROTECTED]>:
> >
> >
> > > They check out bsddb from subversion, see Tools/buildbot/external.
> > > If you don't trust th
On Tue, Feb 26, 2008 at 02:04:47PM -0800, Brett Cannon wrote:
> Or we can get rid of bsddb and not have the problem anymore. =)
+1 for smaller stdlib and fewer problems.
Oleg.
--
Oleg Broytmannhttp://phd.pp.ru/[EMAIL PROTECTED]
Programmers don't die, th
On Feb 26, 2008, at 5:04 PM, Brett Cannon wrote:
> Or we can get rid of bsddb and not have the problem anymore. =)
+1 for fewer problems. :)
-Fred
--
Fred Drake
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mail
On Tue, Feb 26, 2008 at 1:52 PM, Facundo Batista
<[EMAIL PROTECTED]> wrote:
> 2008/2/26, "Martin v. Löwis" <[EMAIL PROTECTED]>:
>
>
> > They check out bsddb from subversion, see Tools/buildbot/external.
> > If you don't trust that they did so correctly, edit the script to
> > remove bsddb, che
2008/2/26, "Martin v. Löwis" <[EMAIL PROTECTED]>:
> They check out bsddb from subversion, see Tools/buildbot/external.
> If you don't trust that they did so correctly, edit the script to
> remove bsddb, check that in, wait for them to delete it, then revert
> the script, check in again, and see
> - X86 XP-4: idem. For this two, how can be tried if the bsddb lib in
> those windows is correctly installed?
They check out bsddb from subversion, see Tools/buildbot/external.
If you don't trust that they did so correctly, edit the script to
remove bsddb, check that in, wait for them to delete i
> - Alpha Tru64: test_smtplib.py is flaky, and _ssl.c is not compiled
> correctly. Neil is hunting this, I think.
Last time we looked at the _ssl problem, the machine had an
out-of-date installation of OpenSSL. Don't know if that ever got
rectified; I just crossed that buildbot off my list :-).
2008/2/25, Thomas Hervé <[EMAIL PROTECTED]>:
> I've worked on that problem during the bug day. I've open a ticket with
> a patch at http://bugs.python.org/issue2168.
Most of the buildbots are green now!!!
Thank you all! This community is as awesome as Python itself, ;)
Three remains in red, t
Facundo Batista a écrit :
> 2008/2/25, Facundo Batista <[EMAIL PROTECTED]>:
>
>
>> 2008/2/25, Christian Heimes <[EMAIL PROTECTED]>:
>>
>> > Thomas Herve has worked out a patch: http://bugs.python.org/issue2177
>>
>> After reviewing, testing and etc, I commited it. Let's see the buildbots! :)
>>
2008/2/25, Facundo Batista <[EMAIL PROTECTED]>:
> 2008/2/25, Christian Heimes <[EMAIL PROTECTED]>:
>
> > Thomas Herve has worked out a patch: http://bugs.python.org/issue2177
>
> After reviewing, testing and etc, I commited it. Let's see the buildbots! :)
Some are green, now, but others still ar
2008/2/25, Christian Heimes <[EMAIL PROTECTED]>:
> Thomas Herve has worked out a patch: http://bugs.python.org/issue2177
After reviewing, testing and etc, I commited it. Let's see the buildbots! :)
--
.Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
Facundo Batista wrote:
> All fail in test_compiler.py.
Thomas Herve has worked out a patch: http://bugs.python.org/issue2177
Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
ht
All fail in test_compiler.py.
--
.Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python
88 matches
Mail list logo
