Skip to content

add shebang for py2 , because py3 may be not working#531

Open
KM-200 wants to merge 1 commit intojarvisteach:appJarfrom
KM-200:patch-1
Open

add shebang for py2 , because py3 may be not working#531
KM-200 wants to merge 1 commit intojarvisteach:appJarfrom
KM-200:patch-1

Conversation

@KM-200
Copy link
Copy Markdown

@KM-200 KM-200 commented Aug 27, 2018

py3 was not working for me.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 74.585% when pulling a409336 on KM-200:patch-1 into 9474e66 on jarvisteach:appJar.

@jarvisteach
Copy link
Copy Markdown
Owner

You'll need to raise the pull request against the next_release branch.

I also think it should just be python instead of python2

And it should probably be done in all files in the examples & issues directory?

@KM-200
Copy link
Copy Markdown
Author

KM-200 commented Aug 28, 2018

I am the last one to disagree... my latest bash script version does not corrupt the sources anymore as far as I know.

However, it seems to me, most current distros (say ARCH Linux) run py-3 when "python" is launched, but here "python2" is required specifically, unless the real problem is identified and fixed. Hence my "python2" shebang.

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.

3 participants