[PEAK] dumb question about easy_install

[Michael Bayer]

yeah you know i always plead with my users to write docs too, but it  
happens very rarely.   i tend to work off of things that I see people  
misunderstanding on a regular basis.

i have also seen a core group of users that are really comfortable  
with the whole "setup.py develop" thing, although im not sure if its  
so widely understood.  but it took a totally changed PYTHONPATH  
behavior for me to really bother understanding it....though for this  
particular issue I am just sticking some strategic "sys.path"  
manipulations in some test scripts that I want people to be able to  
run right from a local tarball/checkout.  then they dont have to set/ 
install anything for that particular use case.

"setup.py test" would be even nicer, and the test suite does build on  
unittest, but I am playing some games with unittest to add "setUpAll 
()" and "tearDownAll()" methods to test classes so im not sure if  
"setup.py test" can work that way.....id have to look into it more  
closely.

On Jun 28, 2006, at 8:28 PM, Phillip J. Eby wrote:

> At 08:04 PM 6/28/2006 -0400, Michael Bayer wrote:
>> On Jun 28, 2006, at 7:45 PM, Phillip J. Eby wrote:
>>> mkdir ~/py_lib
>>> export PYTHONPATH=~/py_lib
>>> cd ~/sa020
>>> python setup.py develop -d ~/py_lib
>>
>> yup that works.
>>
>> (insert obligatory "docs need more examples !" here....)
>
> Insert obligatory "patches welcome!" here...  ;)
>
> Actually, the above is more-or-less documented for easy_install but  
> not for setup.py develop.
>
> Frankly, there are certain times and places where I suck at writing  
> adequate documentation, and this is one of them.  I know *way* too  
> much about Python to be able to write these kinds of examples well,  
> because I don't know what it is that people don't know.  There  
> isn't much that *I* can do about it, but this is fertile ground for  
> volunteers to write up their experiences and/or perspectives, since  
> they are a lot closer to the "not knowing" and can thus explain  
> things better for other people who didn't know.  :)
>
> To be quite honest, I've seen the ~/py_lib sort of setup for  
> PYTHONPATH so many times I thought it was a well-established meme  
> in its own right.  I suppose that for people coming from e.g. Java  
> it might not be as obvious, especially in the context of eggs  
> (since .jars have to be put on the classpath individually in Java).
>
>
>> thanks for the help  !
>
> No problem.
>