You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### What does this implement/fix? Explain your changes.
C# naming conventions are different from python naming conventions.
CamelCase is the usual convention for properties and methods in C#,
while snake_case is preferred in python (pep8).
When using ansys-pythonnet to bind C# to python, python users will use
the C# APIs with the C# conventions. This breaks expectations for python
users.
This PR adds an option to enable pep8 aliases for python bindings,
allowing python code to use pep8 even if the C# code does not.
---------
Co-authored-by: Mohamed Koubaa <[email protected]>
Copy file name to clipboardExpand all lines: README.rst
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,3 +7,4 @@ Changes relative to pythonnet:
7
7
* Revert of `#1240 <https://github.com/pythonnet/pythonnet/pull/1240>`_.
8
8
* Opt-into explicit interface wrapping, `#19 <https://github.com/ansys/ansys-pythonnet/pull/19>`_. This opts into the behavior that became the default in #1240 if ToPythonAs<T> is explicitly used
9
9
* Option to bind explicit interface implementations, `#23 <https://github.com/ansys/ansys-pythonnet/pull/23>`_. This provides a runtime option to expose C# explicit interface implementations to Python.
10
+
* Option to bind pep8 aliases `#24 <https://github.com/ansys/ansys-pythonnet/pull/24>`_.
0 commit comments