Bug #1706381: Specifying the SWIG option "-c++" in the setup.py file

(as opposed to the command line) will now write file names ending in
".cpp" too.
This commit is contained in:
Georg Brandl 2007-04-24 15:27:13 +00:00
parent 18afb37845
commit fb4b3b77c7
2 changed files with 6 additions and 1 deletions

View file

@ -533,7 +533,8 @@ class build_ext (Command):
if self.swig_cpp: if self.swig_cpp:
log.warn("--swig-cpp is deprecated - use --swig-opts=-c++") log.warn("--swig-cpp is deprecated - use --swig-opts=-c++")
if self.swig_cpp or ('-c++' in self.swig_opts): if self.swig_cpp or ('-c++' in self.swig_opts) or \
('-c++' in extension.swig_opts):
target_ext = '.cpp' target_ext = '.cpp'
else: else:
target_ext = '.c' target_ext = '.c'

View file

@ -209,6 +209,10 @@ Core and builtins
Library Library
------- -------
- Bug #1706381: Specifying the SWIG option "-c++" in the setup.py file
(as opposed to the command line) will now write file names ending in
".cpp" too.
- As specified in RFC 2616, an HTTP response like 2xx indicates that - As specified in RFC 2616, an HTTP response like 2xx indicates that
the client's request was successfully received, understood, and accepted. the client's request was successfully received, understood, and accepted.
Now in these cases no error is raised in urllib2. Now in these cases no error is raised in urllib2.