-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add the possibility to set a project-specific Python interpreter #1014
Comments
From ccordoba12 on 2012-07-07T15:55:26Z Thanks for the report and sorry for the late response. It's a good idea and certainly a missing feature. We'll try to improve our project functionality for our 2.3 version, to be released next year. Unfortunately we're busy right now on other things for version 2.2. Summary: Feature request: Add the possibility to set a project-specific python interpreter |
From pierre.raybaut on 2013-01-02T07:13:46Z Status: Accepted |
From pierre.raybaut on 2013-01-02T07:14:18Z Summary: Add the possibility to set a project-specific Python interpreter (was: Feature request: Add the possibility to set a project-specific python interpreter) |
From pierre.raybaut on 2013-05-11T05:51:13Z Labels: -MS-v2.3 MS-v2.4 |
@ccordoba12 could this be closed in favor of #11362 ? |
Sure, let's close it. |
From ssalo...@gmail.com on 2012-05-04T03:00:13Z
Currently in spyder 2.2.0dev version there is a global python interpreter setting but no project specific setting. The project specific setting would be used when F5 is used to run the project.
Currently the global setting makes it hard to switch between projects the use separate virtualenvs.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1014
The text was updated successfully, but these errors were encountered: