[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2210: 'sudo pip install .' fails if tests have been run

Tahoe-LAFS trac at tahoe-lafs.org
Wed Apr 2 23:52:27 UTC 2014


#2210: 'sudo pip install .' fails if tests have been run
---------------------------+-------------------------
     Reporter:  daira      |      Owner:
         Type:  defect     |     Status:  new
     Priority:  normal     |  Milestone:  undecided
    Component:  packaging  |    Version:  1.10.0
   Resolution:             |   Keywords:  pip install
Launchpad Bug:             |
---------------------------+-------------------------

Comment (by daira):

 Note that this doesn't happen when installing from an sdist (because
 sdists don't contain `_trial_temp`); it only happens when installing from
 a checkout on which tests have been run. So it is reasonable for
 `MANIFEST.in` not to be consulted, since, IIUC, the purpose of
 `MANIFEST.in` is only to determine what goes into an sdist. However, I
 don't understand why `pip` is looking at directories that were not
 specified in the call to `setuptools.setup`.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2210#comment:2>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list