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

mentos.py uses /usr/bin/python, desires python2. #49

Closed
damianb opened this Issue Nov 2, 2012 · 7 comments

Comments

Projects
None yet
7 participants
@damianb

damianb commented Nov 2, 2012

Not sure how many distros are doing this now, but I know a few are using "python2" to indicate python 2.x nowadays - and some have set /usr/bin/python to mean python 3.x.

@muoji

This comment has been minimized.

Show comment
Hide comment
@muoji

muoji Nov 14, 2012

Archlinux is doing this, and it's causing me problems.

I saw that the call to mentos.py is only done with the path to the file and relying on its shebang to call python. I think it could be not too hard to implement a way to configure pygments to specify a path to python and then using it to call mentos.py.
It would solve the problem for distros that now use /usr/bin/python for python3, without breaking backward compatibility.

muoji commented Nov 14, 2012

Archlinux is doing this, and it's causing me problems.

I saw that the call to mentos.py is only done with the path to the file and relying on its shebang to call python. I think it could be not too hard to implement a way to configure pygments to specify a path to python and then using it to call mentos.py.
It would solve the problem for distros that now use /usr/bin/python for python3, without breaking backward compatibility.

@damianb

This comment has been minimized.

Show comment
Hide comment
@damianb

damianb Jan 3, 2013

PING. Come on, seriously. This is one hell of an annoying problem to leave for months on end. Can't you check to see if the /usr/bin/python2 executable exists in the filesystem and use that over /usr/bin/python?

damianb commented Jan 3, 2013

PING. Come on, seriously. This is one hell of an annoying problem to leave for months on end. Can't you check to see if the /usr/bin/python2 executable exists in the filesystem and use that over /usr/bin/python?

@pidpawel

This comment has been minimized.

Show comment
Hide comment
@pidpawel

pidpawel Jan 23, 2013

Problem exists on Gentoo too.

pidpawel commented Jan 23, 2013

Problem exists on Gentoo too.

@madhatter

This comment has been minimized.

Show comment
Hide comment
@madhatter

madhatter Feb 8, 2013

Another ping. I really would like to have this fixed.

madhatter commented Feb 8, 2013

Another ping. I really would like to have this fixed.

@seven1m

This comment has been minimized.

Show comment
Hide comment
@seven1m

seven1m commented May 1, 2013

+1

@mindfulmonk

This comment has been minimized.

Show comment
Hide comment
@mindfulmonk

mindfulmonk May 5, 2013

For those using rbenv and Arch Linux:
vim .rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/pygments.rb-0.4.2/lib/pygments/mentos.py
and change it to look like this
#!/usr/bin/env python2

mindfulmonk commented May 5, 2013

For those using rbenv and Arch Linux:
vim .rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/pygments.rb-0.4.2/lib/pygments/mentos.py
and change it to look like this
#!/usr/bin/env python2

@tnm

This comment has been minimized.

Show comment
Hide comment
@tnm

tnm Jun 25, 2013

Collaborator

Should be resolved in latest release.

Collaborator

tnm commented Jun 25, 2013

Should be resolved in latest release.

@tnm tnm closed this Jun 25, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment