smcgruer_[EST]: So what's the current status of the Py3 stuff?

As far as we can tell, the rollout has been mostly successful. We caught two regressions, python file handlers that were changed recently and needed to be updated to be py3 compatible

We have already had one problem, in that one of the fixes I submitted for one of the py file handlers turned out to be py3 *only*, and so broke when Chromium tried to import it

So that probably shows that it will be difficult to keep things py2-compatible

Yeah

Thanks for getting the infra change through

Nw

I'm hoping to move Chromium to py3 for WPT in the next week

It's slightly less trivial than I hoped, but I think a hacky solution should get us by :D

Gecko is in the same situation. Turns out that it's not fully trivial, but it looks reasonable to get it done soon

Hmm, exciting android only error with Py3

jgraham: if it's any consolation -- here's our third attempt at fixing web-platform-tests/wpt #26655

Oh god, the Python 3 "if you're using bytes we're going to punish you by type converting indexing operations" thing

also a quick question for you web-platform-tests/wpt #26574#issuecomment-734454000

(sorry not sure if you're working today)

I am!

We got a weird extra holiday covering the first three days this week, which totally makes sense once you realise how the decision was made but makes no sense at all on its own terms

Hexcles: Given that a roll is something you fill with bacon, I'm not entirely sure I understand your question :) Are you saying that the pywebsocket change is from upstream and it could also be landed with an explicit upgrade to the latest upstream?

jgraham: oh sorry. Yes I was asking if you'd like me to do a proper `git subtree` operation directly on master

Or just land the PR as is which contains the identical patch

I feel like future us will thank present us if we do this explicitly with a git subtree operation, but I wouldn't be upset if you just landed the patch.

I was going to send a PR but then I realized I'd need to push master anyway since we don't allow merge commits on GitHub UI

jgraham: yeah it's quite easy to do as well. alright then, I'm pushing to master now :)

Go for it!

done

Thanks for reviewing that py3 change jgraham, and sorry I didn't get to it Hexcles

No problem