On Wed, Jan 28, 2009 at 1:19 PM, rcmn <[email protected]> wrote: > > thank you for the easy_install options. Yes i'll be able to easily get > them all with a firefox add-on. Thank you. > Suggestion for the maintainers : 1 big zip file with a little howto in > it could be handy :-)
Actually, there is some movement on that. I need a nice foolproof installer for my App Engine book, and a zip of preinstalled eggs (aka a Pylons SDK) looks like the answer. It just needs more testing to see whether the same file can work on Windows and Mac as well as my native Linux, or whether we'd need separate ones. (E.g., simplejson's C extensions are platform-specific, but of course they can't be used on App Engine anyway so they'd be excluded from the install. The question is how many other platform-specific oddities are among the Pylons dependencies.) For App Engine we'd have to customize the eggs rather heavily before bundling them up (to remove unnecessary files), but for regular Python they'd need less customization. I can also see multiple install-zips available depending on which optional features you want to use (e.g., deprecated WebHelpers code, bundled documentation, etc). So there is work afoot to offer a one-file Pylons SDK, but there are still some details to test and decide. Another issue is how this can integrate with Virtualenv. Virtualenvs can be made portable, but not transferred to another computer with different system paths, and a virtualenv tarball would contain largish Python C libraries. The next question is whether a Pylons SDK tarball could also include a precreated default application as the Django SDK does. The answer seems to be no because Pylons applications have the application name embedded in the directory structure and egg-info files, so you'd have to make changes in several places. Another semi-related issue is pip (http://python.org/pypi/pip), which is Ian's alternative to easy_install. It has some interesting features but also some lacks compared to easy_install, so we're still comparing it. One of the lacks is the inability to install a prebuilt egg, which is needed on Windows systems that won't install simplejson the normal way. Of course, having a one-file SDK obviates the need for ppl to install Pylons dependencies in the first place, so that if that's successful it would lessen the need for people to use pip or easy_install at all in the tutorial stage. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
