[Rivet] Python 3

[David Grellscheid]

Hi Frank,

I have also switched to a default Py3 system on my laptop, that's where
my sudden interest in fixing it came from. Together with my Py2.7
desktop, I've got both ends covered. And if we're not supporting 2.6
anymore anyway, my problem of a missing test system goes away.

Testing is of course very welcome anyway!

See you,

  David


On 20/11/2017 16:06, Frank Siegert wrote:
> Thanks David for going through this.
> 
> In fact, the differences in string (encoding) handling are exactly why
> I never pushed a complete Python3 transition into the repository. In
> particular the question of backward compatibility was by far
> non-trivial. At this point now, do we agree to not care about Python
> 2.6 users (SL6!) anymore? That's fine by me.
> 
> Have you already implemented the fallbacks for that? I have a system
> with Python3 as default, so could help testing if you want.
> 
> Cheers,
> Frank
> 
> 
> On 20 November 2017 at 14:08, David Grellscheid
> <david.grellscheid at durham.ac.uk> wrote:
>> Hi Andy,
>>
>> 2to3 doesn't cover text IO very much, where Py3 (rightly) forces you to
>> be careful about the encoding, and makes a strongly typed distinction
>> between texts and byte sequences.
>>
>>   David
>>
>>
>> Once it's checked, we can have emoji .info files ;-)
>>
>>
>>
>> On 18/11/2017 12:56, Andy Buckley wrote:
>>> Thanks David. Actually, I thought I'd already done everything flagged
>>> up by 2to3 other than the overzealous list() calls on every returned
>>> iterator... guess I missed some.
>>>
>>> Andy
>>>
>>>
>>> On 17 November 2017 at 22:33, David Grellscheid
>>> <david.grellscheid at durham.ac.uk> wrote:
>>>> Hi all,
>>>>
>>>> I've gone through the core features of YODA and Rivet, and made them
>>>> Python-3-compatible on the default branches. I have not tested all
>>>> helper scripts yet, so if you notice anything odd, please let me know,
>>>> and I'll fix it. I'll go through everything in the next days.
>>>>
>>>> Also, I haven't run a python 2.6 test yet, most likely the UI is broken
>>>> for such old pythons now, and I'm not sure how much effort the
>>>> compatibility would be yet, we'll need to see if it's even worth trying.
>>>> Python 2.7.3 (April 2012) onwards should work.
>>>>
>>>> See you,
>>>>
>>>>   David
>>>> _______________________________________________
>>>> Rivet mailing list
>>>> Rivet at projects.hepforge.org
>>>> https://www.hepforge.org/lists/listinfo/rivet
>>>
>>>
>>>
>> _______________________________________________
>> Rivet mailing list
>> Rivet at projects.hepforge.org
>> https://www.hepforge.org/lists/listinfo/rivet