➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author meador.inge
Recipients eric.araujo, flox, meador.inge, pitrou, vstinner
Date 2011-10-23.17:20:40
SpamBayes Score 7.138107e-09
Marked as misclassified No
Message-id <1319390441.49.0.220252427576.issue13240@psf.upfronthosting.co.za>
In-reply-to
Content 
> Actually, I think sysconfig does the right thing when it comes to all
> the configure-generated HAVE_XXX variables

I agree.  The 'configure' script could be improved, though.  If we truly
want to enable this by default, then the defaulting should be moved to
configure.  This will give a more accurate portrayal in sysconfig.
Also, we can do the USE but !HAVE check in configure, which is better
anyway because the error is caught earlier.

I am thinking something like the attached.  Thoughts?

P.S. We could probably get rid of the HAVE macro all together by doing
all the work in the 'configure' script.
History
Date User Action Args
2011-10-23 17:20:41meador.ingesetrecipients: + meador.inge, pitrou, vstinner, eric.araujo, flox
2011-10-23 17:20:41meador.ingesetmessageid: <1319390441.49.0.220252427576.issue13240@psf.upfronthosting.co.za>
2011-10-23 17:20:40meador.ingelinkissue13240 messages
2011-10-23 17:20:40meador.ingecreate