Bugzilla

:ahal - given that there is nothing using `moztest` in-tree at this point, and the mozbase documentation at [this link](https://firefox-source-docs.mozilla.org/search.html?q=moztest&check_keywords=yes&area=default) doesn't even mention `moztest`, is it worth keeping this in-tree?

FYI, all tests pass in python3.5 right off the bat, no changes necessary. 

So this bug should lead to either:

- removal of `moztest` from tree
- 'enable' python3 for `moztest` by removing `skip-if` from manifest and calling it a day

:ahal - ~~given that there is nothing using `moztest` in-tree at this point, and the mozbase documentation at [this link](https://firefox-source-docs.mozilla.org/search.html?q=moztest&check_keywords=yes&area=default) doesn't even mention `moztest`, is it worth keeping this in-tree?~~

I spoke too soon, there are a couple of places it's being used outside of the `moztest` module itself.

FYI, all tests pass in python3.5 right off the bat, no changes necessary. 

So, this bug should be:
- 'enable' python3 for `moztest` by removing `skip-if` from manifest and calling it a day

:ahal - ~~given that there is nothing using `moztest` in-tree at this point, and the mozbase documentation at [this link](https://firefox-source-docs.mozilla.org/search.html?q=moztest&check_keywords=yes&area=default) doesn't even mention `moztest`, is it worth keeping this in-tree?~~

EDIT: I spoke too soon, there are a couple of places it's being used outside of the `moztest` module itself.

For whoever that works on this (if no one does, I'll just go ahead and make the change) tests all pass, but developer should look at rest of the code and possibly run it through 2to3 converter to identify if any syntax errors exist.

FYI, all tests pass in python3.5 right off the bat, no changes necessary. 

So, this bug should be:
- 'enable' python3 for `moztest` by removing `skip-if` from manifest and calling it a day

:ahal - ~~given that there is nothing using `moztest` in-tree at this point, and the mozbase documentation at [this link](https://firefox-source-docs.mozilla.org/search.html?q=moztest&check_keywords=yes&area=default) doesn't even mention `moztest`, is it worth keeping this in-tree?~~

EDIT: I spoke too soon, there are a couple of places it's being used outside of the `moztest` module itself.

For whoever that works on this (if no one does, I'll just go ahead and make the change) tests all pass on python2/3 currently, but developer should look at rest of the code and possibly run it through 2to3 converter to identify if any syntax errors exist.

~~:ahal - given that there is nothing using `moztest` in-tree at this point, and the mozbase documentation at [this link](https://firefox-source-docs.mozilla.org/search.html?q=moztest&check_keywords=yes&area=default) doesn't even mention `moztest`, is it worth keeping this in-tree?~~

EDIT: I spoke too soon, there are a couple of places it's being used outside of the `moztest` module itself.

For whoever that works on this (if no one does, I'll just go ahead and make the change) tests all pass on python2/3 currently, but developer should look at rest of the code and possibly run it through 2to3 converter to identify if any syntax errors exist.

~~:ahal - given that there is nothing using `moztest` in-tree at this point, and the mozbase documentation at [this link](https://firefox-source-docs.mozilla.org/search.html?q=moztest&check_keywords=yes&area=default) doesn't even mention `moztest`, is it worth keeping this in-tree?~~

EDIT: I spoke too soon, there are a couple of places it's being used outside of the `moztest` module itself.

For whoever that works on this (if no one does, I'll just go ahead and make the change) tests all pass on python2/3 currently, and a good starting point might the patch that's been left up.

~~:ahal - given that there is nothing using `moztest` in-tree at this point, and the mozbase documentation at [this link](https://firefox-source-docs.mozilla.org/search.html?q=moztest&check_keywords=yes&area=default) doesn't even mention `moztest`, is it worth keeping this in-tree?~~

EDIT: I spoke too soon, there are a couple of places it's being used outside of the `moztest` module itself.

For whoever that works on this (if no one does, I'll just go ahead and make the change to strike this one off the list) tests all pass on python2/3 currently, and a good starting point might the patch that's been left up.