[tahoe-dev] [tahoe-lafs] #657: "python ./setup.py test" rebuilds packages

[tahoe-lafs]

#657: "python ./setup.py test" rebuilds packages
-----------------------+----------------------------------------------------
 Reporter:  zooko      |           Owner:  somebody  
     Type:  defect     |          Status:  new       
 Priority:  minor      |       Milestone:  eventually
Component:  packaging  |         Version:  1.3.0     
 Keywords:             |   Launchpad_bug:            
-----------------------+----------------------------------------------------

Comment(by warner):

 ah, this matches what I was experiencing on OS-X last week.

 I guess I'm not surprised that the setuptools 'test' target is doing a
 compile (I can see it helping people who forget/decline to do a 'build'
 first, and I can imagine the setuptools folks believing that their is-a
 -library-already-installed logic working fast enough and correctly enough
 to avoid repeating a lot of work on each test pass). What I am surprised
 about is that it appears to compile+copy things into the working directory
 (which I assume is the root of the source tree). I would expect it to
 compile+copy things into build/lib, and then add that directory to
 PYTHONPATH before running the tests. Isn't that what build/ is for?

 Thanks for the note about how easy it is to manually uninstall things that
 you've allowed setuptools to write to system directories.. that makes me
 feel like I have more control over my system if I had to resort to 'sudo
 setup.py install'.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/657#comment:3>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid