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
The main exception to this is the Qt bindings, which are all C++ style. The accepted convention is to use Python naming for your own code and Qt conventions just for calling/overriding Qt things.
In particular, capital letters and underscores should (almost) never go together. This looks very strange to me.
Also, I suggest avoiding writing the type of a thing in variable names, e.g. the many variables called Button_..... The exception to this is if there is only one thing of a given type around, e.g. a graph_view of type GraphView.
The text was updated successfully, but these errors were encountered:
For consistency (and generally not getting weird-looking code), I suggest we adopt PEP 8 naming conventions where ever possible/reasonable:
https://peps.python.org/pep-0008/#naming-conventions
The main exception to this is the Qt bindings, which are all C++ style. The accepted convention is to use Python naming for your own code and Qt conventions just for calling/overriding Qt things.
In particular, capital letters and underscores should (almost) never go together. This looks very strange to me.
Also, I suggest avoiding writing the type of a thing in variable names, e.g. the many variables called
Button_....
. The exception to this is if there is only one thing of a given type around, e.g. agraph_view
of typeGraphView
.The text was updated successfully, but these errors were encountered: