Fix Python default argument handing broken since swig-3.0.3
Default values are no longer generated as Python code by default. They must be explicitly turned on using the "python:defaultargs" feature. Closes #294 Closes #296 The problems in these two issues when "python:defaultargs" is turned on still need to be fixed and should be addressed in separate patches. The important thing is the default code generation is now fixed.
This commit is contained in:
parent
34787ab98e
commit
38ba81811e
8 changed files with 139 additions and 69 deletions
|
|
@ -5,6 +5,16 @@ See the RELEASENOTES file for a summary of changes in each release.
|
|||
Version 3.0.4 (in progress)
|
||||
===========================
|
||||
|
||||
2015-01-08: wsfulton
|
||||
[Python] Fix #294 #296 - Regression introduced in SWIG-3.0.3 when
|
||||
wrapping functions with default arguments. Now any method with default
|
||||
arguments obtains the default arguments from C++ instead of generating
|
||||
Python code with the default arguments.
|
||||
|
||||
The "python:defaultargs" feature has been introduced for users to
|
||||
optionally generate Python methods with the default arguments instead
|
||||
the default *args.
|
||||
|
||||
2015-01-08: olly
|
||||
Allow C++11 "explicit constexpr". Fixes github issue#284 reported
|
||||
by Paweł Tomulik. Also handle "constexpr explicit" and "constexpr
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue