-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
MAINT chmod ±x #21234
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
MAINT chmod ±x #21234
Conversation
1ed87da
to
61fe7f7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds reasonable, thanks!
What about examples? They start with a shebang, but they're just examples. Some of them are executable, others are not. Typically, should the following be executable or not?
I think it doesn't matter, people should execute them by running python example.py
in any case.
Then remove the shebang. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @DimitriPapadopoulos.
I would actually +1 for that in examples. For instance, #!/usr/bin/python make no sense whatsoever to me. Unless there are some users that double click on examples on Linux or Mac and it works? Could you please open a separate issue about this? |
What does this implement/fix? Explain your changes.
Run
chmod +x
on some files that are supposed to be executable, this is consistent with other similar files:Run
chmod -x
on some files that are not supposed to be executable, again for consistency with other similar files:Any other comments?
What about examples? They start with a shebang, but they're just examples. Some of them are executable, others are not. Typically, should the following be executable or not?
Finally I have kept this file non-executable, because it is "dangerous":
scikit-learn/.binder/postBuild
Lines 10 to 12 in d152b1e