On Mon, Dec 5, 2011 at 6:30 PM, Christoph Zwerschke <[email protected]> wrote: > Am 05.12.2011 15:03, schrieb Alessandro Molina: > >> Any other idea on how to avoid people having to manage a hube bunch of >> packages they really don't care about? > > > We could add upper limits to the version numbers in addition to the lower > limits.
Uhm, but that wouldn't help project authors when they have to upgrade to a new version of TG. Might it be that I'm missing something? Apart from changing the TurboGears package version, they still would have to check one by one all the various packages that are injected inside their setup.py as a consequence of using TG and set them to the right version required by the new TG release. My target is to avoid forcing the user to have to manage the complexity of the packages that are the consequence of our choices. They just want to use TG2.1.1 and they shouldn't be forced to care about which packages TG2.1.1 uses to support auth, db or anything else that is quickstart dependent. > > Sure, in reality, even slight changes can break a TG project. For instance, > I found some of my apps were broken when updating repoze.who.plugins.sa from > 1.0rc2 to 1.0 (http://github.com/repoze/repoze.who-sqlalchemy/issues/1) and > it took me quite some time to identify the cause. Some small changes can > have a big effect. This is one of the reasons why I really think we need a way to lower the complexity of dependencies management for TG projects :) -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en.
