On Thu, 17 Jan 2013 17:19:01 -0000 exar...@twistedmatrix.com wrote: > Absolutely. This issue has been reported in connection to Wokkel > already: > > http://twistedmatrix.com/trac/ticket/6245 > > There is currently a fix proposed and waiting review, and there has > been some discussion about doing a maintenance release of 12.3 to > distribute the fix. Thank you for reporting your experience with > 12.3.0 (although testing during the /pre/-release period would have > saved everyone some trouble :). > > It would be great if you could try out the proposed fix and let us > know if it also addresses the problem with your application.
Sure. I'll test it during this weekend and let you know if it solves the problem. > Since some concern has been voiced over the effort necessary to do a > 12.3.1 release (as opposed to just including this fix in 13.0), I'd > also be interested to know whether one or the other of those would be > more helpful for you - does anything prevent you (or your users) from > upgrading to 13.0 once it is released? There's nothing which prevents me from upgrading from 12.x to 13.0 so I think that after testing the proposed patch properly fixes the issue I can just wait for the 13.0 release. Thanks, -- Angelo Dell'Aera 'buffer' Antifork Research, Inc. http://buffer.antifork.org Sysenter Honeynet Project http://www.sysenter-honeynet.org _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
