original) (raw)
(On Thu, Sep 26, 2013 at 1:45 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:
"make touch"? Wow, I'm learning new stuff everyday :-)On Thu, 26 Sep 2013 11:46:07 -0700
Eli Bendersky <eliben@gmail.com> wrote:
\> > >> 2013/9/26 Eli Bendersky <eliben@gmail.com>:
\> > >> > Hi All,
\> > >> >
\> > >> > Earlier this morning I had a slight tackle with a couple of the 3.4
\> > bots
\> > >> > (sorry everyone!). I fixed some problems in asdl.py -
\> > >> > http://hg.python.org/cpython/rev/21d46e3ae60c - and used the 'with'
\> > >> > statement. Some bots don't have Python 2.6+ and couldn't bootstrap
\> > >> > Python-ast.h/c
\> > >> >
\> > >> > Two questions:
\> > >> >
\> > >> > \* Should I always check-in Python-ast.h and Python-ast.c when I touch
\> > >> > asdl\*
\> > >> > ? The generated files are unchanged, it's only the timestamp that
\> > >> > changed.
\> > >> > \* Can we, in theory, use new Pythons for asdl\* code, because
\> > >> > Python-ast.\*
\> > >> > are, in fact, checked in so they don't have to be rebuilt by the bots
\> > or
\> > >> > users?
\> > >>
\> > >> We should have the buildbots run "make touch", so they don't need to
\> > >> run asdl\_c.py.
\> > >
\> > >
\> > > How should we go about doing this?
\> >
\> > Complain to Antoine I suppose. :)
\> >
\> \[+ Antoine\]
\> Done :)
(what point is there in adding things to Makefile if nobody knows about
them?)
The devguide would be a good place to mention this. http://bugs.python.org/issue15964 tracked the task for a while, but I'm not sure what the status is.
Eli