Skip to content
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

shebang fix. #3

Merged
merged 1 commit into from
Nov 2, 2016
Merged

shebang fix. #3

merged 1 commit into from
Nov 2, 2016

Conversation

jNullj
Copy link
Contributor

@jNullj jNullj commented Jul 13, 2016

!/usr/bin/env python calles python 2

!/usr/bin/env python3 should be used insted

after testing it on my linux server i realised i forgot about this.

#!/usr/bin/env python calles python 2
#!/usr/bin/env python3 should be used insted
@bentasker
Copy link
Owner

Doi, yes - my test VM only had 3 installed :D

@ghost
Copy link

ghost commented Nov 2, 2016

Hi Bentasker.. Just cloned this repo.. I think you could update the readme to specify that one should use python3 to run the script.

@bentasker bentasker merged commit a47d1ff into bentasker:master Nov 2, 2016
@bentasker
Copy link
Owner

Yes, you're right, I got sidetracked and forgot to update (or, it seems, merge). Both done now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants