[Distutils] svn tagging setuptools command

[Ian Bicking]

Phillip J. Eby wrote:
> At 03:07 PM 8/28/2005 -0500, Ian Bicking wrote:
> 
>> I don't know if setup.py is the right frontend for all of these.  One
>> specific issue is that one command creates the basic framework of a
>> package, including a setup.py file.  But maybe setuptools could be
>> extended to support two kinds of entry points: one that is applied
>> globally (what it currently has), and one that is applied only on demand
>> (for framework-specific commands).
> 
> 
> My thought is that at some point (0.7?) setuptools will have a 'nest' 
> script that runs general-purpose commands, and it will have its own 
> entry point group for commands to install, list, uninstall, etc.

I suppose this would be a good place for a command to setup a new 
project (since that's kind of package management -- at least 
chronologically); would it be an appropriate entry point for other more 
project-specific commands?  It doesn't seem like it to me; but then 
setup.py seems appropriate for those commands.

I think for the command plugins, I'd imagine:

setup(
   ....
   setup_plugins=['spec1', 'spec2', ...])

Which writes to .egg-info/setup_plugins.txt (one line per requirement). 
  Then it includes any 'distutils.extra_commands' entry points from 
those eggs, which act exactly like distutils.commands.

Or maybe it could be something in setup.cfg?  I'd actually find this 
sort of thing quite awkward in setup.py, since setup.py can't be 
(reasonably) written to.

Incidentally, is it possible to put setup.cfg in the .egg-info directory 
or somewhere?  It messes up tab completion.

-- 
Ian Bicking  /  ianb at colorstudy.com  / http://blog.ianbicking.org