On 2015-04-24 08:41, Adi Roiban wrote:
> Hi,
>
> I feel that twisted.python.compat is slowly duplicating / reinventing
> an important part of the six code.
>
> Code which does not import from twisted.python.compat will have all
> kind of ad-hoc / in module code to handle differences between py2
On 24 Apr 2015, at 8:41, Adi Roiban wrote:
I feel that twisted.python.compat is slowly duplicating / reinventing
an important part of the six code.
I’m +1 on this too. I was a bit hesitant in the past but duplicating
compatibility code everywhere is becoming ridiculous and a hassle.
__
On 24 April 2015 at 08:00, Glyph wrote:
>
>> On Apr 24, 2015, at 02:41, Adi Roiban wrote:
>>
>> Hi,
>>
>> I feel that twisted.python.compat is slowly duplicating / reinventing
>> an important part of the six code.
>>
>> Code which does not import from twisted.python.compat will have all
>> kind
> On Apr 24, 2015, at 02:41, Adi Roiban wrote:
>
> Hi,
>
> I feel that twisted.python.compat is slowly duplicating / reinventing
> an important part of the six code.
>
> Code which does not import from twisted.python.compat will have all
> kind of ad-hoc / in module code to handle differences
