- It's best to install packages within a virtualenv as much as possible (for applications or projects that you're working on). This keeps the dependencies separate and as such you should only install things globally when that's appropriate (but often it's not because a dependency is specific to a project).
It's best to install packages within a virtualenv as much as possible (for applications or projects that you're working on). This keeps the dependencies separate and as such you should only install things globally when that's appropriate (but often it's not because a dependency is specific to a project).
But to answer your question: it's indeed possible that some dependencies are systemwide and others are in the virtualenv. It's a bit weird to have systemwide Python, user Python and virtualenv Python working together but it can be done. Try to avoid spreading out your dependencies everywhere because that's hard to maintain. Combining brew / pip is also a recipe for disaster as they're not always aware of each other and they interfere indeed. I use MacPorts (or Homebrew) for non-Python dependencies and Python interpreter installation and pip for all Python packages.
It doesn't sound right: you should not have to edit the hashbang of a file (unless, of course, as a workaround for a package that was released with a bug). Updating a PYTHONPATH variable is normal as many have such modifications in their shell profile. Your edit to the file is not sustainable as upgrades or other changes may break things again. Provided you're using a correctly packaged release you shouldn't have to point to another Python interpreter.
But to answer your question: it's indeed possible that some dependencies are systemwide and others are in the virtualenv. It's a bit weird to have systemwide Python, user Python and virtualenv Python working together but it can be done. Try to avoid spreading out your dependencies everywhere because that's hard to maintain. Combining brew / pip is also a recipe for disaster as they're not always aware of each other and they interfere indeed. I use MacPorts (or Homebrew) for non-Python dependencies and Python interpreter installation and pip for all Python packages.
- It doesn't sound right: you should not have to edit the hashbang of a file (unless, of course, as a workaround for a package that was released with a bug). Updating a PYTHONPATH variable is normal as many have such modifications in their shell profile. Your edit to the file is not sustainable as upgrades or other changes may break things again. Provided you're using a correctly packaged release you shouldn't have to point to another Python interpreter.
- It's best to install packages within a virtualenv as much as possible (for applications or projects that you're working on). This keeps the dependencies separate and as such you should only install things globally when that's appropriate (but often it's not because a dependency is specific to a project).
But to answer your question: it's indeed possible that some dependencies are systemwide and others are in the virtualenv. It's a bit weird to have systemwide Python, user Python and virtualenv Python working together but it can be done. Try to avoid spreading out your dependencies everywhere because that's hard to maintain. Combining brew / pip is also a recipe for disaster as they're not always aware of each other and they interfere indeed. I use MacPorts (or Homebrew) for non-Python dependencies and Python interpreter installation and pip for all Python packages.
- It doesn't sound right: you should not have to edit the hashbang of a file (unless, of course, as a workaround for a package that was released with a bug). Updating a PYTHONPATH variable is normal as many have such modifications in their shell profile. Your edit to the file is not sustainable as upgrades or other changes may break things again. Provided you're using a correctly packaged release you shouldn't have to point to another Python interpreter.
It's best to install packages within a virtualenv as much as possible (for applications or projects that you're working on). This keeps the dependencies separate and as such you should only install things globally when that's appropriate (but often it's not because a dependency is specific to a project).
But to answer your question: it's indeed possible that some dependencies are systemwide and others are in the virtualenv. It's a bit weird to have systemwide Python, user Python and virtualenv Python working together but it can be done. Try to avoid spreading out your dependencies everywhere because that's hard to maintain. Combining brew / pip is also a recipe for disaster as they're not always aware of each other and they interfere indeed. I use MacPorts (or Homebrew) for non-Python dependencies and Python interpreter installation and pip for all Python packages.
It doesn't sound right: you should not have to edit the hashbang of a file (unless, of course, as a workaround for a package that was released with a bug). Updating a PYTHONPATH variable is normal as many have such modifications in their shell profile. Your edit to the file is not sustainable as upgrades or other changes may break things again. Provided you're using a correctly packaged release you shouldn't have to point to another Python interpreter.
- It's best to install packages within a virtualenv as much as possible (for applications or projects that you're working on). This keeps the dependencies separate and as such you should only install things globally when that's appropriate (but often it's not because a dependency is specific to a project).
But to answer your question: it's indeed possible that some dependencies are systemwide and others are in the virtualenv. It's a bit weird to have systemwide Python, user Python and virtualenv Python working together but it can be done. Try to avoid spreading out your dependencies everywhere because that's hard to maintain. Combining brew / pip is also a recipe for disaster as they're not always aware of each other and they interfere indeed. I use MacPorts (or Homebrew) for non-Python dependencies and Python interpreter installation and pip for all Python packages.
- It doesn't sound right: you should not have to edit the hashbang of a file (unless, of course, as a workaround for a package that was released with a bug). Updating a PYTHONPATH variable is normal as many have such modifications in their shell profile. Your edit to the file is not sustainable as upgrades or other changes may break things again. Provided you're using a correctly packaged release you shouldn't have to point to another Python interpreter.