Diez B. Roggisch wrote:
> You should consider using setuptools. Then you get an egg that people
> can install, and you can define "console_scripts"-entry-points which
> will be installed into /usr/local/bin or similar locations.
Interesting, I think I need to have a play with that. The cross pl
Peter Chant schrieb:
Krishnakant wrote:
Have you considered creating a deb or rpm package for your application?
Most of the documentation for deb or rpm will talk about make files.
But even a distutil based python package (with a setup.py) can be made
into a deb package.
Then the your requirem
Krishnakant wrote:
> Have you considered creating a deb or rpm package for your application?
> Most of the documentation for deb or rpm will talk about make files.
> But even a distutil based python package (with a setup.py) can be made
> into a deb package.
> Then the your requirement will be sa
On Sun, 2009-08-02 at 20:21 +0100, Peter Chant wrote:
> What is a good way to do this? There are instructions on making modules at:
>
> http://docs.python.org/distutils/setupscript.html
>
> however, what do you do if you don't want a module? I'm thinking of where
> I'd like to split the code in
What is a good way to do this? There are instructions on making modules at:
http://docs.python.org/distutils/setupscript.html
however, what do you do if you don't want a module? I'm thinking of where
I'd like to split the code into several files and have a build / setup
script put it together a
