On 10.10.2019 23:12, Nathan Hartman wrote:
> On Thu, Oct 10, 2019 at 4:54 PM Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
>> Nathan Hartman wrote on Thu, Oct 10, 2019 at 16:28:21 -0400:
>>> If we have to pull that item out (not saying we do yet, just IF), then that
>>> leaves us with no Python tasks. I'd like to have something Python-related
>>> on the list because there's a good chance that a 700+ member university
>>> hackathon will have some Python programmers. Any other suggested
>>> Python tasks we could add?
>> Something in the test harness. For example, make it easier to run «make check»
>> with client version ≠ server version, to actually test on-the-wire
>> compatibility. Or use trunk client and trunk server, but make them both expose
>> fewer capabilities, to test that compatibility codepaths.
> Has any work been done on making the test harness Py3 compatible?
> If not, then perhaps a Py2 -> Py3 port is something that should be on the
> list. Even if a 2 day hackathon is not enough time, even making a dent in
> that will be a helpful thing.
The test harness (and other build-related stuff) has been compatible
with Python3 for quite a few years now.
-- Brane
Received on 2019-10-11 01:14:58 CEST