More specifically we need this piece - https://github.com/mozilla-releng/funsize-balrogworker/blob/master/bin/balrogworker.py switched over to python 3.5. It'll have to cope with http://hg.mozilla.org/build/tools/file/tip/lib/python/balrog/submitter once this is migrated as well.

Dumping some more IRC content for later use. mtabara> bhearsum: is there a bug for http://hg.mozilla.org/build/tools/file/tip/lib/python/balrog/submitter migration to 3.5 I could look at? 20:24:26 <~bhearsum> there's no concrete plans to do that AFAIK 20:24:42 <~bhearsum> i think it's most likely to happen if/when that code moves into the balrog repo 20:27:22 <mtabara> do we have a plan for that? 20:28:04 <~bhearsum> nope 20:28:12 <~bhearsum> just a fanciful wish 20:33:12 <mtabara> how much of an effort you'd say adding tools/lib/python3/balrog/submitter scripts would be? 20:34:10 <~bhearsum> probably not much since i wrote https://github.com/mozilla/balrog/blob/master/agent/balrogagent/client.py already 20:35:10 <~bhearsum> i'm not 100% convinced the current api.py should simply be ported to python3, though 20:35:22 <~bhearsum> and cli.py may be tougher to port 20:36:06 <~bhearsum> i think it's worth taking a fresh look at lib/python/balrog to see if we can improve it if it's getting rewritten in python3

Just to be clear, until we have the http://hg.mozilla.org/build/tools/file/tip/lib/python/balrog/submitter migrated in a separated balrog py3 client, we won't be able to migrate to py3 the existing https://github.com/mozilla-releng/balrogscript/blob/master/bin/balrogworker.py since it's using the tools py2 repo. Will leave this open until some day we'll address that.