| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@dipinknair @RobPasMue @SMoraisAnsys please review |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks fine by me - but I may not be super proficient in the internals of what this implementation may cause as side effect
Sorry, something went wrong.
|
Good thing is that it is an opt-in feature 😄 |
Sorry, something went wrong.
I was planning to start by making it an opt-in feature for PyMechanical too. Maybe a kwarg in the App constructor. cc @dipinknair |
Sorry, something went wrong.
Please do - let's not roll it out by default (yet) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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.