Occasionally, I run into glitches installing or updating Python packages on my system using pip (on OS X) but find that I can install the troublesome packages in a virtualenv (that employs the same version of Python as my system) and then copy them over to my system packages, where they seem to work fine.
Is there any reason not to do this (at least as a stopgap for packages I urgently need)? Does the package installed in the virtualenv incorporate any information about the virtualenv that would cause it to misbehave among the system packages (e.g. if the virtualenv was deleted)? Will information about the presence of the copied package be missing from the system installation (i.e., is there information saved there about the packages that have been installed other than what's in the packages themselves)?
Occasionally, I run into glitches installing or updating Python packages on my system using pip (on OS X) but find that I can install the troublesome packages in a virtualenv (that employs the same version of Python as my system) and then copy them over to my system packages, where they seem to work fine.
Is there any reason not to do this (at least as a stopgap for packages I urgently need)? Does the package installed in the virtualenv incorporate any information about the virtualenv that would cause it to misbehave among the system packages (e.g. if the virtualenv was deleted)? Will information about the presence of the copied package be missing from the system installation (i.e., is there information saved there about the packages that have been installed other than what's in the packages themselves)?
0 commentaires:
Enregistrer un commentaire