I think we have a fundamental problem with Python-ast.c and
Python-ast.h. These files should not be both auto-generated and checked
into Subversion. The problem is that if you do a make distclean,
these files will get removed and svn stat will give you a ! flag. Of
course, you can svn up to get
On 1/2/06, Barry Warsaw [EMAIL PROTECTED] wrote:
I think we have a fundamental problem with Python-ast.c and
Python-ast.h. These files should not be both auto-generated and checked
into Subversion.
I agree with the problem statement.
The general rule should be that no file that is ever
On Mon, 2006-01-02 at 15:16 -0800, Neal Norwitz wrote:
The Python-ast.[ch] should probably not be removed by distclean. This
is similar to configure. Would that make you happy? What else would
improve the current situation?
I think it would, without causing bootstrapping issues.
-Barry
Here's some info on setting up buildbot
http://www.python.org/dev/buildbot/. These instructions should be
cleaned up and put in the developers faq. Right now, the only person
that can generate/assign buildbot names/passwords is Martin AFAIK.
We currently have 4 slaves setup:
Linux: x86 and
test_bsddb3 fails for me with BSD DB 4.1 and 4.2 on gentoo Linux. I
think it has for a long time. Is anyone else seeing these failures?
You must use -u bsddb when running regrtest.
4.2 has 2 failures:
test02_associateAfterDB
(bsddb.test.test_associate.ShelveAssociateRecnoTestCase)
On 1/2/06, Neal Norwitz [EMAIL PROTECTED] wrote:
On 1/2/06, Barry Warsaw [EMAIL PROTECTED] wrote:
I think we have a fundamental problem with Python-ast.c and
Python-ast.h. These files should not be both auto-generated and checked
into Subversion.
I agree with the problem statement.
I've updated the script that builds python and the docs, runs the
tests, and copies everything up to docs.python.org. Currently, this
only works for the trunk. I'm not sure if there's much of a benefit
to set this up for branch(es) also.
The docs are here:
http://docs.python.org/dev/
The
Neal We currently have 4 slaves setup:
Neal Linux: x86 and amd64 (gentoo 2.6, glibc 2.3)
Neal Solaris10 sparc
Neal OS X: G5 (not yet working, need to setup path to svn)
The G5 *was* working. I changed nothing at my end. Got a mail yesterday
from Martin. It looks like PATH
On 1/2/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The G5 *was* working. I changed nothing at my end. Got a mail yesterday
from Martin. It looks like PATH lost /usr/local/bin (where the Metissian
installer puts the svn executable). I added a /usr/bin/svn symlink, but
would really
On Jan 2, 2006, at 10:30 PM, Neal Norwitz wrote:
On 1/2/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The G5 *was* working. I changed nothing at my end. Got a mail
yesterday
from Martin. It looks like PATH lost /usr/local/bin (where the
Metissian
installer puts the svn
I've put an instance of Commentary up against the full 2.4
documentation: http://pythonpaste.org/comment/python24/
It writes to a Subversion repository so you can see what the backend
data looks like: http://pythonpaste.org/comment/svn/python24/ -- not
much there yet. Obviously things like
I had a friend run regrtest -L on Mac OSX a while ago. There are
several memory leaks which still appear to be an issue. There are a
bunch of leaks reported from putenv which I'm not sure how to fix
The attached patch should correct one of the problems. Can someone
with a Mac test it? I'll
12 matches
Mail list logo
