Changes between Version 2 and Version 3 of Ticket #50058, comment 6
- Timestamp:
- Feb 8, 2016, 5:21:00 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #50058, comment 6
v2 v3 2 2 3 3 One should NOT use pip to install packages on the macports directory tree (which is what a macports-installed pip would do by default!). The recommended procedure would be: 4 * Install with macports your python distribution and its pip (and probably its virtualenv) 5 * Prepare a new place to install pip packages (like a virtualenv) 6 * Use pip to install the packages into the new place 4 * Install with macports your python distribution 5 * if that python doesn't have its own standard virtualenv and pip (like Python 3.4 and later include venv and ensurepip), then install with macports the appropriate pip and virtualenv for that python 6 * Prepare a "new place" to install pip packages (like a virtualenv) 7 * Once into the "new place", use pip to install whatever 7 8 8 9 A possible, but risky exception, would be: macports not carrying a pip-available package that has to be installed globally. That package could then be installed through pip into the macports directory tree, without fear of causing a conflict - until the day that macports *does* carry that package, and then the risk of conflict appears. Right?