On Thu, 2011-03-03 at 17:45 -0500, Mark Ramm wrote: > > A countervailing opinion: pip has problems with namespace packages. For > > an example, trying to use tox (a testing package which uses pip > > internally) to run tests against a namespace package (like > > repoze.anything) consistently fails. I haven't had time (or > > inclination) to dig into this purely because easy_install *does* work > > fine for these kinds of packages, but the failure tox may be compelling > > enough for me to dig into why pip fails under some circumstances related > > to namespace packages. > > I think the reason PIP has trouble with namespace packages is the > choice to always use single-version-externally-managed. > > In my experience, if you install EVERYTHING with pip, you're ok, or if > you install everything without it, you are OK, but using it along side > distribute and easy install.
Seems unlikely that this is the same problem, because tox does indeed use pip exclusively internally into a virtualenv it creates itself, so there is no mixing going on. - C -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
