On Thu, Dec 15, 2011 at 11:33 AM, Christoph Zwerschke <[email protected]> wrote: > Am 15.12.2011 11:09, schrieb Alessandro Molina: >> >> That is the reason why I think that setting the precise version number >> >> inside requirements of the TurboGears package would make life easier >> for new users. > > > Yes, we discussed this already. Assume we had hardwired a Pylons 1.0 > requirement and 1.0.1 brings substantial fixes, would it still be possible > to upgrade or would you get requirement conflict errors?
Right, you would get a conflict error. even though I think this is greatly reduced by a frequent release cycle. > With the private > index and lax requirements a fresh installation works out of the box, but > people still have the freedom to update dependencies from PyPI. This is > particularly important if there is no TG update for month (which happened in > the past) or if people are stuck with older TG versions when our API changes > and they don't find the time to adapt their applications. They still want to > be able to update individual components if these have important fixes. Can't we provide both? Nothing prevents us from releasing on pypi a package with frozen versions and keep the private index with a package that has minimum versions requirements. I think that this is the way that would make easy for newcomers to install the framework and possible for experts to tune it. It just requires a very little extra effort from us when preparing a new release. -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
