Re: [Twisted-Python] [Twisted] #7598: Port twisted.spread.pb to Python3

> On Aug 2, 2016, at 4:38 AM, Wolfgang Rohdewald > wrote: > > Am Dienstag, 2. August 2016, 03:39:58 CEST schrieb Glyph Lefkowitz: >> Probably we should up-convert from bytes automatically in the places >> where we know python will be using the values as identif

Re: [Twisted-Python] [Twisted] #7598: Port twisted.spread.pb to Python3

Am Dienstag, 2. August 2016, 03:39:58 CEST schrieb Glyph Lefkowitz: > Probably we should up-convert from bytes automatically in the places > where we know python will be using the values as identifiers, including > callRemote and the keys in a __dict__. Attached is some grep for my port showing

Re: [Twisted-Python] [Twisted] #7598: Port twisted.spread.pb to Python3

> On Aug 2, 2016, at 01:45, Wolfgang Rohdewald > wrote: > > Am Donnerstag, 28. Juli 2016, 11:27:15 CEST schrieb Twisted: >> #7598: Port twisted.spread.pb to Python3 > > did you test with client on Python2 and server on Python3 and vice versa? > > Not a bug report, but anyway ... This was clie

Re: [Twisted-Python] [Twisted] #7598: Port twisted.spread.pb to Python3

Am Donnerstag, 28. Juli 2016, 11:27:15 CEST schrieb Twisted: > #7598: Port twisted.spread.pb to Python3 did you test with client on Python2 and server on Python3 and vice versa? Not a bug report, but anyway ... This was client with Python3, server with Python2 The same works with my old port to