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

Invalid python interpreter #3

Closed
thomas-mangin opened this issue Aug 27, 2013 · 2 comments
Closed

Invalid python interpreter #3

thomas-mangin opened this issue Aug 27, 2013 · 2 comments
Labels

Comments

@thomas-mangin
Copy link
Member

From sebastie...@gmail.com on December 08, 2011 01:25:42

On archlinux, python 2.7 interpreter is call python2 an not python. In previous version (pre 2.x.y), interpreter was detected setup.py caller and set correctly.

In new version, exabpg is become a script shell and interpreter is detected by a which python. It's python 3 on archlinux.

Can we have a way to define current python interpreter path correctly ?

Original issue: http://code.google.com/p/exabgp/issues/detail?id=3

@thomas-mangin
Copy link
Member Author

From thomas.mangin on December 07, 2011 17:45:41

should fixed in mercurial and made available on updated 2.0.1 release

Status: Fixed

@thomas-mangin
Copy link
Member Author

From thomas.mangin on November 16, 2012 02:06:00

Status: Done

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

No branches or pull requests

1 participant