"Martin v. Loewis" wrote: > > > > > Shouldn't the define be placed into the pyconfig.h file or > > > > only in those extensions which need it ? > > > > > > Wouldn't it cause the same trouble there? > > > > No, because the pyconfig.h import is under extension control > > (e.g. you can first include the system or lib header files > > and only then import pyconfig.h). > > Of course, doing so would be really stupid. Python.h *must* be the > first include, or things may break. Why should "things break" ? I've doing this for years in lots of Python extensions... Back on topic: how are we going to get -DINET6 out of the Makefile ? -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Consulting & Company: http://www.egenix.com/ Python Software: http://www.lemburg.com/python/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4