![]() |
|
|
|||||||
![]() |
Python - Building / making an application |
|
|
Thread Tools | Search this Thread |
|
|
#1 |
|
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 and install it somewhere such as /usr/local/bin. I'm interested in what the standard way of doing this is. Thanks, Pete -- http://www.petezilla.co.uk Peter Chant |
|
|
|
|
#2 |
|
Posts: n/a
|
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 into several files and have a build / setup > script put it together and install it somewhere such as /usr/local/bin. > I'm interested in what the standard way of doing this is. > 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 satisfied at least for most gnu/linux based distros. happy hacking. Krishnakant. Krishnakant |
|
|
|
#3 |
|
Posts: n/a
|
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 satisfied at least for most gnu/linux > based distros. I'm a slacker, so what I would do would be to make a slack build, the slackbuild would take the source and build that. The stage I am at is the "how to build the source" stage. Don't really intend to get as far as distribution specific packages. What I could do is create a script in the source root directory (that sounds a bit overblown) that simply concatenates together all the python files in the right order and perhaps copies the result to /usr/local/bin or /usr/bin as appropriate. Is that the right way to go? It looks like distutils is appropriate only for modules. OTOH it might be appropriate to put the bulk of an application in a module and have a function calling it the only part of the main script. Pete -- http://www.petezilla.co.uk Peter Chant |
|
|
|
#4 |
|
Posts: n/a
|
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 requirement will be satisfied at least for most gnu/linux >> based distros. > > I'm a slacker, so what I would do would be to make a slack build, the > slackbuild would take the source and build that. The stage I am at is > the "how to build the source" stage. Don't really intend to get as far as > distribution specific packages. > > What I could do is create a script in the source root directory (that sounds > a bit overblown) that simply concatenates together all the python files in > the right order and perhaps copies the result to /usr/local/bin or /usr/bin > as appropriate. Is that the right way to go? It looks like distutils is > appropriate only for modules. > > OTOH it might be appropriate to put the bulk of an application in a module > and have a function calling it the only part of the main script. 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. Diez Diez B. Roggisch |
|
|
|
#5 |
|
Posts: n/a
|
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 platform bit could be useful as well. Pete -- http://www.petezilla.co.uk Peter Chant |
|
![]() |
| Thread Tools | Search this Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| standalone .net application | jass | Software | 1 | 04-02-2009 03:11 AM |
| How to open Web Application pages (ASPX) in Windows application. | arameshmca | Software | 1 | 02-07-2008 03:18 AM |
| Server Error in '/Forms' Application. | AxleWack | General Help Related Topics | 0 | 10-11-2007 01:47 PM |
| How to revert file to unknown application | perezla | General Help Related Topics | 1 | 09-12-2007 03:15 AM |
| ASP.NET with User Interface Process Application Block | robinp | Software | 0 | 03-05-2007 10:01 AM |