-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python nodes ending in .py #79
Comments
The recommendation from the Please consider to update the wiki pages with this recommendation and post the links to changes pages in this ticket.
This statement is much less clear imo. I don't think this is a generally accepted approach. I might be better to remove the recommendation from the Please consider to contribute a PR for catkin to update the docs. |
I believe users need to preserve the .py files because as they're following a tutorial they might need to change their codes later on. Here you might need to trade customizability with neatness. |
The file extension has no influence on whether you can edit it or not. |
But how will they know about the file type if there's no extension |
The shebang should tell file explorers and you can always open it. The fact that it is in the source package makes it very likely that it's not a binary. |
Currently, the catkin python install how to explicitly states:
However, the tutorials create nodes ending in
.py
. Now, the question is: which one applies?If they indeed should not end in
.py
(which I personally would support because as the author of the catkin howto wrote, that's an implementation detail and not really relevant to the user), it would make sense if the Wiki Tutorials would either not create nodes ending in.py
because most people will follow the tutorials when they create their own nodes or at least have a section about how normally you would strip the extension.Edit: I just noticed that the catkin howto also proposes putting nodes in a nodes subfolder and other python scripts in a scripts subfolder which is also not consistent with the tutorials.
The text was updated successfully, but these errors were encountered: