On Tue, Feb 15, 2011 at 9:21 AM, Christoph Zwerschke <[email protected]> wrote:
> Am 15.02.2011 14:47, schrieb Alessandro Molina: > > On Tue, Feb 15, 2011 at 2:34 PM, [email protected] > > <[email protected]> wrote: > >>> Both the methods you suggest have been tried before and both have > >> failed. > >> "Forcing our pypi index, has the opposite problem, if there is a mayor > >> security release, or something that unbreaks something that broke > >> really bad (look for the Extremes package for an example of how it was > >> broken in our pypi and fixed in regular pypi. > > > > We have off course to keep our pypi updated when fixes for the > > libraries that we use appear. This shouldn't be a problem as we use TG > > ourselves and so we know when it won't install anymore. > > I wanted to answer the same, I don't see the problem with the approach > itself, but with us failing to properly maintain our own PyPI. > > -- Christoph > > It shouldn't be too difficult to whip up a script that will at least notify someone (or maybe even create a ticket) when new versions of packages show up on PyPI. Of course, whoever gets notified has to actually _DO_ something about it, but at least that part can be automated somewhat. Perhaps other bits can be automated as well. Maybe there should be a TG-based private PyPI app that can be told to check for new versions? And then "expose" them to the private PyPI when instructed to? Perhaps it could take some kind of switch or something so that devs/testers would get the latest version of all packages, while the general users would get only the approved versions? I'm just kind of brainstorming here. Kevin Horn -- 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.
