Also, might I suggest that, at least for purposes of debugging, you use a virtualenv (or a throwaway VM if you prefer) and install a copy of Twisted from this decade. Twisted is very stable, and fixes lots of bugs in every release. So you're fairly unlikely to uncover *new* problems, but very likely to fix the problem you're seeing, by doing so. Dustin On Wed, Jun 4, 2014 at 3:20 PM, Glyph Lefkowitz <glyph@twistedmatrix.com> wrote:
On Jun 4, 2014, at 2:03 AM, Franz Schwartau <franz@electromail.org> wrote:
I know twisted 8.2.0 is quite old. Unfortunatly there are no newer RPM in RHEL/CentOS or even EPEL.
Yeah, RHEL is kind of a bummer.
I could provide the complete code. But it would be laborious to set up everything. You'd need postfix, ppolicy, mysql, etc. It would be easier (for you) if I'd set up a VM.
If you need more than MySQL + Twisted alone to reproduce the bug, then I would suggest that perhaps you haven't tracked it down far enough to do useful investigations within Twisted... I appreciate that you're willing to set up a VM, but the interesting thing is to extract the problem into a simple example, not to get the whole ball of mud running :).
-glyph _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python