Author kirkshorts
Recipients kirkshorts
Date 2008-11-07.13:58:02
SpamBayes Score 3.63221e-11
Marked as misclassified No
Message-id <1226066300.29.0.700541757582.issue4279@psf.upfronthosting.co.za>
In-reply-to
Content
With a clean checkout of the py3k source it fails to build the Parser 
exension module (based on Modules/parsermodule.c) when building against 
a cygwin target.

This appears to be related to the movement of the symbol 
_PyParser_Grammar from graminit.c to Parser\metagrammar.c. (At least 
this is where it was going by the code comments)

Because of this the module now requires Parser\metagrammar.c to get 
this information via Py_meta_grammar.

The patch modifies setup.py to add the required file and modifies 
parsermodule.c to use the accessor function.

(This fails on a clean trunk build in the same way as well - which 
makes me very suspicious that this is not a "real" issue as the 
buildbots seem to be green.)

My gut feeling is that my modification to setup.py for the module is 
incorrect - it just looks messy. So I await the inevitable: "That's not 
how to fix it...." :-)
History
Date User Action Args
2008-11-07 13:58:20kirkshortssetrecipients: + kirkshorts
2008-11-07 13:58:20kirkshortssetmessageid: <1226066300.29.0.700541757582.issue4279@psf.upfronthosting.co.za>
2008-11-07 13:58:04kirkshortslinkissue4279 messages
2008-11-07 13:58:03kirkshortscreate