On Feb 19, 1:42 pm, Ian Bicking <[EMAIL PROTECTED]> wrote: > primco wrote: > > This page:http://code.google.com/p/django-buildout/wiki/ProjectLifecycle > > > has a tutorial for creating a buildout for django. I'm interested in > > trying something like this (I'm using workingenv right now but it's > > not working on windows) > > What's not working on Windows? There was a script problem which should > be fixed in 0.6.2/3. >
The problems I was experiencing are solved. Thanks! > > but I'm wondering in anyone else here would be > > interested in this or want to collaborate. We could make a > > contribution to the Pylons wiki with the results. Seems like the > > django tutorial is a good start. > > > I think this would be a promising solution for bundling up Pylons with > > your app for redistribution if the complexity was hidden. I'm not > > great at setuptools and very wary of > > thishttp://cheeseshop.python.org/pypi/zc.buildout > > page. Those instructions are crazy. Do they expect normal humans to > > use this tool if your day job isn't professional setuptools package > > manager? > > I've tried to use zc.buildout a couple times. It's pretty complex, and > I felt like I spent a lot of time debugging my build. It does make it > possible to do things like build other kinds of software (with > configure/make/make install). But building other software doesn't > actually make all the software work together, so I was unimpressed -- > it's useful if you want to build MySQL or Apache, but if you want to > build a C library and get it linked together, it's not easy. > If you try it, note that it won't install scripts unless you tell it to > install the package (i.e., PasteScript) -- including it as a dependency > won't include the script. You might have to jump through some other > hoops too. What's your feeling about PJE basically saying workingenv was an unsupported hack? He seems to back the approach of zc.buildout more. In the posts I've read, PJE seems to recommend using only the setuptools features to get isolated package installs. To me, the lower- level approach you've taken that deals with the platform-specific issues inherent in python is more straightforward (although to a newbie, all the site.py hacking is probably bewildering). This may be off topic but I keep running into these issues with Pylons because of the large number of dependencies and rapid changes in the versions of software throughout the dependency tree. I've been forced to learn more about setuptools than I'd like just to manage my development environment and release process in a way I'm comfortable with. You can't always run off the head revision of 15 packages. At some point you have to freeze it and release it. davep --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
