I would start by asking to Ben Bangert if there is any consideration about releasing a bugfix version of Pylons. Maybe they are not against doing it but they don't have many reasons to do it.
About TG approach, to such issues, as far as I have seen in the past the solution has been to monkeypatch Pylons. Anyway there are places where TG doesn't practically rely on pylons (like template rendering) so I would suggest to start removing pylons dependency from those places so that we can minimize the impact of pylons issues. On Fri, Sep 30, 2011 at 4:27 AM, Michael Pedersen <[email protected]> wrote: > So, I did some research on this ticket: > https://sourceforge.net/p/turbogears2/tickets/110/ > As it turns out, we have compatibility issues, and our first real issue > that's due to Pylons basically stopping. What do you all want to see happen? > I've listed the options in this > comment: https://sourceforge.net/p/turbogears2/tickets/110/?limit=10&page=0#2798 > Thoughts, everyone? > > -- > Michael J. Pedersen > My IM IDs: Jabber/[email protected], AIM/pedermj022171 > Yahoo/pedermj2002, MSN/[email protected] > My Online Resume: http://www.icelus.org/ > Twitter: pedersentg > > -- > 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. > -- 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.
