Nope.<div><br></div><div>It wouldn't be excessively hard to do, once some of the sillier missing methods on bytes objects are fixed -- it's just not very much of a priority. Twisted is used for a lot of production apps which often aren't even deployed on recent versions of 2.x, let alone 3.x, so supporting 2.x properly is far more a priority than supporting 3.x.<div>
<br><div>64 bit vs 32 bit shouldn't be a problem since Twisted is just Python.</div><div><br></div><div>lvh</div></div></div>