mirror of https://github.com/python/cpython
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:
parent
18afb37845
commit
fb4b3b77c7
|
@ -533,7 +533,8 @@ class build_ext (Command):
|
|||
if self.swig_cpp:
|
||||
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'
|
||||
else:
|
||||
target_ext = '.c'
|
||||
|
|
|
@ -209,6 +209,10 @@ Core and builtins
|
|||
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
|
||||
the client's request was successfully received, understood, and accepted.
|
||||
Now in these cases no error is raised in urllib2.
|
||||
|
|
Loading…
Reference in New Issue