This allows us to break things up into modular parts and makes things easier to ship

Comment on attachment 8546942 [details] PR 27288: handle new marionette import Sorry for the delay in getting to this. It's quite an extensive change, and I'm guessing that it will be temporary - ultimately moving over to the marionette_driver package once it's available. I wonder if there's a way to do this in one go without the try/except? Could we release a new version of marionette-client with marionette_driver available? Then a future release would remove this in favour of the separately installable package?

Currently I can't land marionette_driver, therefore release it, because it is failing gaiatests on treeherder. I think having the try/except allows us to upgrade everything everywhere and then release and if people don't update then it uses one or other and we can notify that in the next release they MUST update. At some point we are going to have to update the gaiatests to use marionette_driver package, I think this way does it nicely and people won't be aware of it when it first lands.

Couldn't the current marionette client offer a marionette_driver package that essentially just masquerades as the marionette package? That way you could just switch to marionette_driver before the separate driver package is ready to ship. I just think a try/except for every file is a little ugly, but if you don't feel like we can avoid it then let's continue with this approach. I think a test maintainer would be better to review this patch though, as it will affect imports for any patches in review or to be written. Also, this will rot quickly so will need some coordination to land it.

Comment on attachment 8546942 [details] PR 27288: handle new marionette import Except for the 2 non-blocking nits all looks OK to me.