On Mon, 09 Jul 2018 at 16:59:36, Lukas Fleischer wrote:
> So, we should either rewrite the test cases to explicitly use python2
> or, even better, keep using python and make the tests work with both
> Python 2 and Python 3, the latter of which is achieved by the two
> patches I submitted. Any ratio
On Sun, 08 Jul 2018 at 23:29:47, Mathieu Lirzin wrote:
> Mathieu Lirzin writes:
>
> > Lukas Fleischer writes:
> >
> >> On Sat, 07 Jul 2018 at 23:45:27, Mathieu Lirzin wrote:
> >>> Lukas Fleischer writes:
> >>>
> >>> > As of Python 3.5, but unoptimized and optimized bytecode are stored
> >>> >
Mathieu Lirzin writes:
> Lukas Fleischer writes:
>
>> On Sat, 07 Jul 2018 at 23:45:27, Mathieu Lirzin wrote:
>>> Lukas Fleischer writes:
>>>
>>> > As of Python 3.5, but unoptimized and optimized bytecode are stored
>>> > within .pyc files; .pyo files are no longer generated. Update the Python
Lukas Fleischer writes:
> On Sat, 07 Jul 2018 at 23:45:27, Mathieu Lirzin wrote:
>> Lukas Fleischer writes:
>>
>> > As of Python 3.5, but unoptimized and optimized bytecode are stored
>> > within .pyc files; .pyo files are no longer generated. Update the Python
>> > tests such that the test do
On Sat, 07 Jul 2018 at 23:45:27, Mathieu Lirzin wrote:
> Lukas Fleischer writes:
>
> > As of Python 3.5, but unoptimized and optimized bytecode are stored
> > within .pyc files; .pyo files are no longer generated. Update the Python
> > tests such that the test do not fail if .pyo files are missin
Lukas Fleischer writes:
> As of Python 3.5, but unoptimized and optimized bytecode are stored
> within .pyc files; .pyo files are no longer generated. Update the Python
> tests such that the test do not fail if .pyo files are missing.
Like in other message, it is important that the test suite pa
