On Thu, 2005-09-08 at 19:21 -0700, Jason Huggins wrote: > Jason F. McBrayer wrote: > > Hi. I've more-or-less finished a django app that might be useful to > > other people > <snip, snip> > > I'd like to package this for other people in a way that is as convenient > > for them as possible, while not requiring too much work from me. So, > > what do people expect from a third-party django app by way of packaging? > > The Python world is slowly catching on to using Python "eggs" and the > "cheeseshop" (gosh, I hate that name-- I'll henceforth only call it > "The Shop".)
Don't like the bouzouki player? Yes, I've been noticing the use of eggs and ez_setup. Good and bad points. Good: usually gets dependencies for you. Bad: breaks ./setup.py bdist_rpm, which is how I normally install Python libraries. I'll look at app-packaging as an egg, but I suspect that for a django app the more practical option will be along the lines of "unpack this tarball in your apps directory, run this script to set up the database, add to your installed apps by hand"... -- +----------------------------------------------------------------+ | Jason F. McBrayer [EMAIL PROTECTED] | | "If you wish to make Pythocles wealthy, don't give him more | | money; rather, reduce his desires." -- Epicurus |
