ok, looking at this more, "pip uninstall" wasn't added until v0.6, so probably it just used `--record` for it's log as a side-effect of the previous decision to use `--single-version-externally-managed`. and the decision to use `--single-version-externally-managed`, was probably just based on pip needing to override the dependency resolution, and have it's signature "requirements file" feature that supported overriding dependencies.
On Fri, Nov 15, 2013 at 1:16 PM, Marcus Smith <[email protected]> wrote: > Under the covers, pip uses "setup.py install --record" (which requires > also using --single-version-externally-managed) in order to create an > install log, that get's used for uninstalls. > > And due to using `--single-version-externally-managed`, the install is > done "old-style", i.e., not installed as an egg, and not knowing how to > install *from* an egg. the one caveat being that setuptools (not pip) does > throw in an .egg-info directory with the project metadata. > > So is "pip uninstall" the primary historical reason for the lack of egg > install support? or is there more to the story? > > Marcus >
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
