#43638: py27-virtualenvwrapper: Does not use virtualenv with appropriate suffix ------------------------------------------+-------------------------------- Reporter: audvare@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: virtualenv virtualenvwrapper | Port: ------------------------------------------+-------------------------------- {{{ virtualenvwrapper.sh-2.7 }}} is installed and can be sourced but it does not seem to want to use {{{ virtualenv-2.7 }}} but instead wants to use {{{ virtualenv }}} (no suffix). Maybe this is hard-coded. It may be unnecessary to suffix {{{ virtualenvwrapper.sh }}} with a version for these reasons: - It is inconsistent to not have {{{ mkvirtualenv-2.7 }}}, {{{ rmvirtualenv-2.7 }}} as commands - {{{ virtualenvwrapper }}} is made for all relevant versions of Python (although I have no idea if it is a separate package per version, especially 2 vs 3) - {{{ mkvirtualenv }}} accepts a {{{-p}}} argument for the path of which Python implementation to use: {{{mkvirtualenv -p /usr/bin/python some- name}}} (if you really wanted to) - If {{{virtualenvwrapper.sh}}} is not suffixed, it means shell configurations (bashrc) that are made to be compatible with many OS's do not need a special clause for the MacPorts version The 'fix' to {{{virtualenvwrapper.sh-2.7}}}'s {{{mkvirtualenv}}} is to use symlinks to virtualenv and relevant applications like pip. I have a script attached that creates such symlinks assuming that the version desired is 2.7. I am currently running it every so often with launchd or manually. -- Ticket URL: <https://trac.macports.org/ticket/43638> MacPorts <http://www.macports.org/> Ports system for OS X