At 09:55 AM 3/13/2006 +0200, Ville Vainio wrote:
I'm thinking of the extreme "scaling down" scenario here, shipping only a single .py file (a "script"). When you have a setup.py script you need to bundle it with the module.
When in the past you had a directory full of .py scripts that you added to PATH, now you could just go there and do easy_install *.py.
I'm not following why that would be any better. Why not just add a setup.py to that directory?
On 3/13/06, Phillip J. Eby <pje@telecommunity.com> wrote:
I'm not following why that would be any better. Why not just add a setup.py to that directory?
It's a slight drag to create, esp. if you need to keep it up-to-date when you make changes to directory layout, add/delete scripts etc. and the scripts are not necessarily related to each other (each script is standalone). Basically what I'm saying is that I'm lazy. Perhaps if there was find_modules and find_entrypoints (like there is find_packages now) I wouldn't care, but now creating and maintaining a setup.py is an extra complication. I guess creating my own setuppy-wizard would solve this issue in a cleaner fashion. -- Ville Vainio - vivainio.googlepages.com vainio.blogspot.com - g[mail | talk]='vivainio'
participants (2)
-
Phillip J. Eby -
Ville Vainio