Commit 0e8bae14 authored by Georg Brandl's avatar Georg Brandl

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.
 (backport from rev. 54941)
parent 0a519740
...@@ -533,7 +533,8 @@ class build_ext (Command): ...@@ -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'
......
...@@ -12,6 +12,10 @@ What's New in Python 2.5.2c1? ...@@ -12,6 +12,10 @@ What's New in Python 2.5.2c1?
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.
- Patch #1695229: Fix a regression with tarfile.open() and a missing name - Patch #1695229: Fix a regression with tarfile.open() and a missing name
argument. argument.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment