Bug 1567642 Comment 7 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Actually, let's just co-opt this bug (there are likely going to be many more of these types of errors until we fix this, so no point in keeping the title).

Basically we have two options:

1) Block on bug 1473498 and then convert `mach lint` itself to Python 3
2) Spawn a py3 subprocess from within the lint integration (note currently flake8 is invoked in-process)

I'm tempted to say let's do 1) as that's something we'll want to do anyway and it gives us more motivation to get around to it.. but this might actually be a pretty big issue as more things start becoming Python 3 only, so 2) might be necessary as a stop-gap. I guess we'll see how often
Actually, let's just co-opt this bug (there are likely going to be many more of these types of errors until we fix this, so no point in keeping the title).

Basically we have two options:

1) Block on bug 1473498 and then convert `mach lint` itself to Python 3
2) Spawn a py3 subprocess from within the lint integration (note currently flake8 is invoked in-process)

I'm tempted to say let's do 1) as that's something we'll want to do anyway and it gives us more motivation to get around to it.. but this might actually be a pretty big issue as more things start becoming Python 3 only, so 2) might be necessary as a stop-gap. I guess we can wait and see how often people run into this as we work through `mach` stuff in the meantime.

Back to Bug 1567642 Comment 7