[Python-Dev] serious bug in new import X as Y code

[Thomas Wouters]

On Fri, Aug 18, 2000 at 08:42:34PM +0200, Fredrik Lundh wrote:
> sjoerd wrote:

> > The problem was that because of your (I think it was you :-) earlier
> > change to have a Makefile in Grammar, I had an old graminit.c lying
> > around in my build directory.  I don't build in the source directory
> > and the changes for a Makefile in Grammar resulted in a file
> > graminit.c in the wrong place.

> is the Windows build system updated to generate new
> graminit files if the Grammar are updated?

No, and that's one more reason to reverse my patch ! :-) Note that I didn't
*add* the Makefile, I only added Grammar to the
directories-to-run-make-in-by-default. If the Grammar is changed, you
already need a way to run pgen (of which the source rests in Parser/) to
generate the new graminit.c/graminit.h files. I have no way of knowing
whether that is the case for the windows build files. The CVS tree should
always contain up to date graminit.c/.h files!

The reason it was added was the multitude of Grammar-changing patches on SF,
and the number of people that forgot to run 'make' in Grammar/ after
applying them. I mentioned adding Grammar/ to the directories to be made,
Guido said it was a good idea, and noone complained to it until after it was
added ;P I think we can drop the idea, though, at least for (alpha, beta,
final) releases.

> or is python development a unix-only thingie these days?

Well, *my* python development is a unix-only thingie, mostly because I don't
have a compiler for under Windows. If anyone wants to send me or point me to
the canonical Windows compiler & debugger and such, in a way that won't set
me back a couple of megabucks, I'd be happy to test & debug windows as well.
Gives me *two* uses for Windows: games and Python ;)

My-boss-doesn't-pay-me-to-work-on-Windows-ly y'rs,

-- 
Thomas Wouters <thomas@xs4all.net>

Hi! I'm a .signature virus! copy me into your .signature file to help me spread!