[Distutils] Adding entry points into Distutils ?

[Chris Withers]

Paul Moore wrote:
> 2009/5/9 Chris Withers <chris at simplistix.co.uk>:
>> +1.
>>
>> <flame>Anyone who's arguing against this is either not deploying stuff in a
>> repeatable fashion, and so isn't serious in my books, or is so serious that
>> they're cutting vm images to roll out and so dump everything for the app in
>> site packages</flame>
> 
> Hmm. I'll accept the flame to the extent that I don't deploy stuff to
> a wide enough audience to be qualified to comment on that side of
> things. But:
> 
> 1. Can you clarify what "this" is?

Given that I'm writing this offline on a train, the answer is "no", I'm 
afraid ;-)

> Part of the issue I see is that
> there's never a clear enough statement of a proposal for a non-expert
> in the field to follow.

Which proposal do you think isn't clear enough?

> 2. Distutils is for distributing python modules/packages, so
> *application* deployment is out of scope.

Python applications rely on packages and modules. Application in the 
scope I'm using it might mean something like "YouTube".

> Script support is for
> small-scale stuff (in my view).

Wrong. I use it for creating start/stop scripts for services along with 
scripts to stick in crontabs. I don't need to bother with that for 
small-scales stuff.

> 3. Accepting that I don't know what you mean by "this", can I point
> out that as a user, I personally have problems with a significant
> proportion of scripts distributed with packages - so are you saying
> that those packages "aren't serious",

Probably, or certainly that their authors don't really care about the 
scripts they generate...

> or that there is no way of doing
> what they (and I) want at present?

I'm afraid I don't remember/understand what you want...

> I'll see if I can find some in due course. (Basically, the types of
> things I see are scripts distributed on Windows with no filetype
> extension, .bat wrappers for command line scripts which don't work
> right when called from another bat file, setuptools-built exe wrappers
> which result in version-specific binaries for pure-python code, to
> give some examples).

The last is the "right" thing. These scripts work cross-platform and are 
tied to the correct version of python for the setup as "originally 
intended", ie: the version the package was installed with.

cheers,

Chris