Julian schrieb: > SWIG seems to have done it properly by checking to see if it has been > defined already (which, I think, is how python should do it as well) > Now, even if I am not using SWIG, I could imagine these being defined > elsewhere (by other headers/libraries) or even by setting them in the VS2005 > IDE project settings (which I actually do sometimes). While these are *just* > warnings and not errors, it would look cleaner if pyconfig.h would check if > they were defined already. Sure; I have fixed this now in r52817 and r52818 I just wondered why you get the warning: you shouldn't get one if the redefinition is the same as the original one. In this case, it wasn't the same redefinition, as SWIG was merely defining them, and Python was defining them to 1. Regards, Martin
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