Great release guys, but I wish you hadn’t moved all the comments/help into the functions for the chopExecute/DatExecute etc. I find myself having to delete them every time before I can write code, to keep it cleaner they are also mostly replicated for each function, preferred them before all the built ins, like they were previously. Small thing but I don’t see why they have to be there.
We made them that way because it’s more Pythonic, but if a lot of people dislike it it can certainly be changed back. Open call for feedback here…
No please don’t go back, its great the way it is now. Thank you very much for taking the effort and writing all of those callbacks properly with type hinting and docstrings. I think now its done the way it should be. 
2 Likes
I agree with @soma-cg Chris. As a beginner python guy I like short and sweet and all those extra lines to delete just annoy me. A few hints up top make more sense to me, easy to delete in one block.
Personally I think that inline documentation is never a bad thing.
If people have terser callbacks they prefer they can just drag and drop them into the network and replace the callback.
While I understand that it’s a bit irritating for people who prefer to have more spartan looking source files, the struggle for properly documented code is very real and tends to swing the other way. Discarding documentation in the interest of aesthetics would be a regression in my view.
2 Likes
I would prefer it be optional. Maybe add it to the Preferences.
1 Like
Love the idea of adding this to preferences! I also found myself deleting the extra lines.
1 Like