Re: code packaging

[EMAIL PROTECTED] (John J. Lee) writes: > You can go further: in addition to developing a Debian package (or a > few of them) for your own project, build your OS image using > debootstrap (you'll probably want your own local repository(ies), for > reproducibility). Then you do your development in

Re: code packaging

On 7/22/07, Ryan Ginstrom <> wrote: > Hi Alex: > > Do you develop for Windows? Are you looking to automate a build > process? > > The standard library's build module is distutils: > http://docs.python.org/lib/module-distutils.html > > As I mentioned in my post, I use a variety of third-party mo

RE: code packaging

"Ryan Ginstrom" <[EMAIL PROTECTED]> wrote in news:[EMAIL PROTECTED]: >> On Behalf Of Paul Rubin >> I'm wondering how other projects go about this. > > I develop an automated build system from the very beginning. Running > the build script: > * Creates the API documentation (epydoc) > * Creates t

Re: code packaging

Paul Rubin writes: [...] > I'm now wondering where this type of thing is best addressed in more > general terms. What I usually see happening, in projects I've worked > on and in others, is that developers get the code working on their own > computers, using source contr

RE: code packaging

> On Behalf Of Paul Rubin > I'm wondering how other projects go about this. I develop an automated build system from the very beginning. Running the build script: * Creates the API documentation (epydoc) * Creates the help files (extracting some information from the source) * Builds a windows exec

Re: code packaging

Paul Rubin writes: > Is this appropriate? Inappropriate? Do your projects start using > serious packaging and distribution tools very early in development, > before the code is anywhere near usable? Should they? Yes. Test-driven development has taught me that putting

Re: code packaging

Hello Paul, > I'm now wondering where this type of thing is best addressed in more > general terms. What I usually see happening, in projects I've worked > on and in others, is that developers get the code working on their own > computers, using source control tools and (if we're lucky) tests > d

code packaging

I've been through this kind of thing a few times in the past and received excellent advice here on clpy about how to deal with specific technical aspects (e.g. how to use setuptools, InnoSetup, etc). I'm now wondering where this type of thing is best addressed in more general terms. What I usua