-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Support alternate framework names on OSX #113
Comments
Appearently I cannot attach files to issues, I have a patch that implements this feature by changing the code that checks for Python.framework in sys.prefix by more generic code. |
If you have a github repo with the patch on link to that using the github flavoured markdown described here (and above the edit box of comments): http://github.github.com/github-flavored-markdown/ If you don't you can paste the patch as a gist https://gist.github.com/ and link here. That just seems to be how the github issue tracker works I'm afraid. |
The patch is at: https://gist.github.com/919377 |
Is this related to #609? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions. |
Python 2.6 and later support alternate basenames for a python framework using the --with-framework-name. This can be used to install multiple build variations of python as a framework.
It would be nice if virtualenv supported this.
The text was updated successfully, but these errors were encountered: