Thanks for your reply :) This may be a big ask... but could you briefly outline the steps I would need to take to download pyramid debug toolbar from github and apply the patch; and following this how I would update it for future tagged releases?
I'm very happy to read any documentation. Previously I've only used git for day-to-day versioning of my own projects - an understanding of the overall process I'm aiming for here would really help confidence and perhaps allow me (and others out there) to maintain their pyramid packages better. At the moment I have pyramid_debugtoolbar 0.9.4 installed via pip. Happy to report to this thread (and/or github tracking) how I get on with debugtoolbar and jinja2 with i18n requirements. All the best, Simon At the moment, I have Pyramid 1.2.1 installed via pip. On 14 Nov 2011, at 10:39, Christoph Zwerschke wrote: > Am 14.11.2011 11:02, schrieb Simon Yarde: >> A temporary patch/workaround would be really useful, other than turn off >> debugging :) > > Here is a patch for this issue, let us know how it works: > https://github.com/Pylons/pyramid_debugtoolbar/pull/43 > > -- Christoph > > > > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to pylons-discuss@googlegroups.com. > To unsubscribe from this group, send email to > pylons-discuss+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
