summaryrefslogtreecommitdiff
path: root/Source/Modules/python.cxx
Commit message (Collapse)AuthorAgeFilesLines
* Avoid unused parameter self warningJulien Schueller2023-01-271-1/+1
|
* SwigType * handling corrections - Python builtin manglingWilliam S Fulton2022-11-181-19/+27
| | | | | | | | | | | | Further corrections to pass SwigType * to methods expecting types instead of passing readable type strings. Swig_string_mangle() takes a generic String *, but it was calling functions that require SwigType *. Swig_string_mangle_type() is now provided for SwigType *. The previous commit is a pre-requisite in order to prevent duplicate symbols from being generated in the C++ wrappers.
* Cleanup SWIG_VERSION definitionWilliam S Fulton2022-10-131-1/+1
| | | | | | | | | | | | | Add Swig_obligatory_macros which must be called by each target language to define SWIG_VERSION correctly in the generated code, as well as the language specific macro SWIGXXX where XXX is the target language name. Drop the #ifdef SWIGXXX that was previously generated - I can't see the point of this and if users are defining this macro somehow, then users will need to change this Closes #1050
* Improve director unwrap detection for the return typeWilliam S Fulton2022-10-101-21/+3
| | | | | | | | | | | | | Resolve the return type to correctly determine if the type is a pointer or reference to a director class. SwigType_refptr_count_return() recently added as a simpler fix is no longer needed. The conventional approach of using the "type" rather than "decl" to analyse the return type is used instead too. Issue #1823
* Merge branch 'director-unwrap-result'William S Fulton2022-10-071-3/+1
|\ | | | | | | | | * director-unwrap-result: Unwrap director classes only when returning a pointer or reference to an object
| * Merge branch 'master' into director-unwrap-resultOlly Betts2022-03-011-54/+87
| |\
| * | Unwrap director classes only when returning a pointer or reference to an objectThomas Reitmayr2020-06-201-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | This involves properly counting the number of references and pointers in the return type of a function and only generate unwrapping code if this number is 1. For template instances some post-processing code is added to fix the 'decl' and 'type' attributes of functions if changed in an unfavorable way during template expansion. This commit fixes swig#1811.
* | | Use https for swig.org linksOlly Betts2022-10-061-1/+1
| | |
* | | Generate richcompare switch statements in sorted orderWilliam S Fulton2022-09-301-2/+4
| | |
* | | Add initialisers for additional members in PyHeapTypeObjectWilliam S Fulton2022-08-011-0/+11
| | | | | | | | | | | | (builtin mode) for Python-3.11 - _ht_tpname, _spec_cache.
* | | Header file tidyupWilliam S Fulton2022-05-071-3/+2
| | | | | | | | | | | | | | | Fix Visual C++ warning in scilab.cxx: warning C4996: 'strtok': This function or variable may be unsafe.
* | | [Python] Replace tp_print with tp_vectorcall_offset slot for Python 3.8Kris Thielemans2022-04-211-0/+4
| | | | | | | | | | | | | | | | | | | | | The tp_print slot is no longer supported and replaced with tp_vectorcall_offset. The (printfunc) cast that we used caused problems on PyPy. Fixes #2262
* | | Recognise and ignore Doxygen group commands @{ and @}Olly Betts2022-04-071-4/+10
| | | | | | | | | | | | Fixes #1750
* | | Remove some unnecessary empty lines from generated .py fileWilliam S Fulton2022-04-071-8/+12
| | |
* | | Remove unused functions in Python builtin modeWilliam S Fulton2022-04-071-50/+53
| | |
* | | Remove legacy USE_THISOWN conditional compilationWilliam S Fulton2022-04-061-18/+0
| | | | | | | | | | | | | | | Seems to be a left over from 'thisown' partial removal in 985adc13fba238405028361a8d8e35e8b1b1008c
* | | Slight performance improvement for %pythonnondynamicWilliam S Fulton2022-04-061-3/+3
| | | | | | | | | | | | Setting this is much more likely than thisown
* | | Doxygen comments take precedence over the autodoc feature.William S Fulton2022-04-061-22/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a "docstring" feature is present it will still override a Doxygen comment. If the "autodoc" feature is also present, the combined "autodoc" and "docstring" will override the Doxygen comment. If no "docstring" is present then the "autodoc" feature will not be generated when there is a Doxygen comment. This way the "autodoc" feature can be specified and used to provide documentation for 'missing' Doxygen comments. Closes #1635
* | | Merge branch 'feature/python-builtin-separate-runtime-data'William S Fulton2022-03-261-0/+3
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * feature/python-builtin-separate-runtime-data: Rework swig_and_compile_multi_cpp makefile helper Different capsule names for builtin changes entry Use different capsule names with and without -builtin Conflicts: CHANGES.current
| * | | Use different capsule names with and without -builtinEugene Toder2022-03-181-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Types generated with and without -builtin are not compatible. Mixing them in a common type list leads to crashes. Avoid this by using different capsule names: "type_pointer_capsule" without -builtin and "type_pointer_capsule_builtin" with. See #1684
* | | | Remove minimum Python version checkWilliam S Fulton2022-03-251-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The version checking was historically done to deal with different versions and importing the low-level Python module. Then it was used to try and help when using -py3. A minimum version check implies that the wrappers work with any version >= 2.7, which is not really correct. The correct thing to do is to check that the exact version used matches the one that the C layer was compiled against, which can only be left for the user to do, perhaps using %pythonbegin. Issue #1779
* | | | Remove -py3 command line optionWilliam S Fulton2022-03-231-16/+7
| | | | | | | | | | | | | | | | Closes #1779
* | | | Remove option to use Python 3 only syntax for %pythonnondynamic featureWilliam S Fulton2022-03-231-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A metaclass is added using a decorator @_swig_add_metaclass which is designed to provide a metaclass that works for both Python 2 and Python 3. The option to use the Python 3 only syntax: metaclass=_SwigNonDynamicMeta via the -py3 command line option has been removed as part of a simplification to remove the -py3 option. Issue #1779
* | | | Add Python < 3.3 support for pyabc.iWilliam S Fulton2022-03-231-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | pyabc.i for abstract base classes now supports versions of Python prior to 3.3 by using the collection module for these older versions. Python-3.3 and later continue to use the collections.abc module. The -py3 option no longer has any effect on the %pythonabc feature.
* | | | Python -flatstaticmethod correctionsWilliam S Fulton2022-03-211-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Correct logic for suppressing static methods. Previous logic was missing director disown methods. Add changes file entry for -flatstaticmethod. Closes #2137
* | | | Enable flat static constructor methodsJim Easterbrook2022-03-181-1/+1
| | | | | | | | | | | | | | | | | | | | These are needed to provide renamed overloaded constructors and the like.
* | | | Use flat static method if it's a "friend"Jim Easterbrook2022-03-181-6/+7
| | | | | | | | | | | | | | | | This allows the friends test case to pass, with or without -builtin.
* | | | Python: Option to generate flat class methodsJulien Schueller2022-03-181-4/+9
|/ / /
* | | Add DOH Exit() and SetExitHandler()Olly Betts2022-03-061-9/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Exit() is a wrapper for exit() by default, but SetExitHandler() allows specifying a function to call instead. This means that failures within DOH (e.g. Malloc() failing due to lack of memory) will now perform cleanup such as removing output files. This commit also cleans up exit statuses so SWIG should now reliably exit with status 0 if the run was successful and status 1 if there was an error (or a warning and -Werror was in effect). Previously in some situations SWIG would try to exit with the status set to the number of errors encountered, but that's problematic - for example if there were 256 errors this would result in exit status 0 on most platforms. Also some error statuses have special meanings e.g. those defined by <sysexits.h>. Also SWIG/Javascript tried to exit with status -1 in a few places (which typically results in exit status 255).
* | | Python: avoid unused SwigMethods_proxydocs var (#2222)Julien Schueller2022-03-031-1/+2
| | | | | | | | | Avoids a warning since 3aa302c08f609ad15a602b32a8c0124eb48861f9
* | | Add support for Python variable annotations as a feature.William S Fulton2022-03-021-12/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Both function annotations and variable annotations are turned on using the "python:annotations" feature. Example: %feature("python:annotations", "c"); struct V { float val; }; The generated code contains a variable annotation containing the C float type: class V(object): val: "float" = property(_example.V_val_get, _example.V_val_set) ... Python 3.5 and earlier do not support variable annotations, so variable annotations can be turned off with a "python:annotations:novar" feature flag. Example turning on function annotations but not variable annotations globally: %feature("python:annotations", "c"); %feature("python:annotations:novar"); or via the command line: -features python:annotations=c,python:annotations:novar Closes #1951
* | | Add property annotationssethg2022-03-021-1/+18
| |/ |/|
* | Python function annotations removed from -py3 option.William S Fulton2022-02-271-4/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Python function annotations containing C/C++ types are no longer generated when using the -py3 option. Function annotations support has been moved to a feature to provide finer grained control. It can be turned on globally by adding: %feature("python:annotations", "c"); or by using the command line argument: -features python:annotations=c The implementation is designed to be expandable to support different annotations implementations. Future implementations could implement something like the following for generating pure Python types: %feature("python:annotations", "python"); or typing module types to conform to PEP-484: %feature("python:annotations", "typing"); Closes #1561 Issue #735
* | [Python] Improve handling of SWIG_Py*Method_NewOlly Betts2022-02-041-8/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The SWIG_PyInstanceMethod_New method is no longer added to wrapped classes except when it's actually needed, which is when (!builtin && fastproxy) is true (which it isn't by default). The SWIG_PyStaticMethod_New method is no longer is now similarly gated - previously only (fastproxy) was checked. Finally the C/C++ functions that implement these were always compiled into the module, but now they're only included if (!builtin && fastproxy) is true. Issue noted by vadz in #2190.
* | [Python] Sort out handling of self parameterOlly Betts2022-02-031-9/+19
| | | | | | | | | | | | | | | | | | | | When not using -builtin, the self parameter is now still made available so that user typemaps can use it. Fixes #967. When using -builtin, fix -Wunused-parameter warnings in the generated wrapper code. See #801. Based on a commit peeled out of #801 by teythoon.
* | [python] Fix GCC -Wunused-variable with -builtinOlly Betts2022-01-271-1/+1
| | | | | | | | Fixes #1697
* | [python] Reject -builtin with -noproxyOlly Betts2022-01-261-0/+5
| | | | | | | | | | | | | | This option combination doesn't make sense, and result in code which doesn't compile. Fixes #1990
* | %callback and Python class access for C++ static member functions fixesWilliam S Fulton2022-01-141-2/+19
| | | | | | | | | | | | | | | | | | | | Fix access to C++ static member functions using Python class staticmethod syntax, such as Klass.memberfunction instead of Klass_memberfunction, when using -fastproxy and -builtin in combination with %callback. The docstring containing the callback pointers were not being patched during module initialisation.
* | [Python] Add missing Python kwargs builtin supportWilliam S Fulton2022-01-141-2/+2
| | | | | | | | | | | | | | | | Accept keyword arguments accessing C++ static member functions when using -builtin and kwargs feature and Python class staticmethod syntax. The missing keyword argument support was only when using the class staticmethod syntax, not when using the flat static method syntax.
* | Fixed crashes when using embedded Python interpreters.John Senneker2021-11-301-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes #2101. There are 3 related changes made here: 1. Move the SWIG_globals() singleton into pyrun from pyint so it is visible to SWIG_Python_DestroyModule(). The static globals varlink has been extracted out of the function so that it can be set to NULL in SWIG_Python_DestroyModule(), which fixes the issue described in #2101. (Now when the second interpreter starts up, the Swig_Globals_global pointer will be NULL, so it knows it has to create a new one.) 2. Remove a Py_DECREF on the globals varlink. The decrement is now performed by DestroyModule(), so there's no need to do it in SWIG_init(). 3. Fixed similar issue with SWIG_Python_TypeCache().
* | Fix ODR violationsOlly Betts2021-09-201-1/+2
| | | | | | | | Detected by compiling with GCC flags `-flto -Wodr`.
* | Remove support for $source and $targetOlly Betts2021-04-301-18/+0
| | | | | | | | | | | | | | | | These were officially deprecated in 2001, and attempts to use them have resulted in a warning (including a pointer to what to update them to) for most if not all of that time. Fixes #1984
* | Eliminate unused Printf argsOlly Betts2021-04-131-3/+5
| |
* | Make -py3 generate a check for Python >= 3.0Olly Betts2021-04-121-2/+7
| | | | | | | | Closes #1777
* | Python -builtin fix wrapping constructors with varargsWilliam S Fulton2021-03-231-4/+4
| | | | | | | | | | | | Fix compilation error when using -builtin and wrapping varargs in constructors Closes #1942
* | Fix few unused variable warningsMichel Zou2021-03-071-0/+1
| |
* | Python 3.9 support for -builtinWilliam S Fulton2020-08-271-0/+4
|/ | | | | Add missing initializer for member ‘_heaptypeobject::ht_module’ to complete Python 3.9 support.
* Fix generated Python code for Doxygen comments with triple quotesVadim Zeitlin2020-03-041-0/+10
| | | | | | | | In addition to the changes in the previous commit, also avoid syntax errors in the generated Python docstrings by splitting them into several parts if there are 3 quotes in a row in the input, as it's impossible to have them inside triple-quoted strings, generally speaking (i.e. if there are occurrences of both """ and ''' inside the string).
* Fix generated Python code for Doxygen comments ending with quoteVadim Zeitlin2020-03-041-3/+17
| | | | | | Single-line Doxygen comments ending with a double quote resulted in syntactically-invalid Python docstrings in the output, so use triple single quotes as delimiters in this case to avoid it.
* Fix crash in Python backend when using empty docstringsVadim Zeitlin2020-01-301-4/+11
| | | | | | | | | | | | | Due to confusion in build_combined_docstring(), we could call DohDelete() on the "feature:docstring" string, which resulted in a crash when trying to use it later. Fix this and simplify the code at the same time by ensuring that we always use a copy of "feature:docstring" if it's not empty or don't use it at all if it's empty -- like this we don't have to check for its length each time before using it. Closes #1648.
View Lorry Controller Status