Upcoming rename of the marionette-client package to marionette-harness

[Henrik Skupin]

Hi,

Please note that we will soon rename the marionette-client Python
package to marionette-harness. This work is currently happening on bug
1320073. The reason for it is that there is lots of confusion between
the package names and the folder names in-tree:

> testing/marionette/client -> marionette-driver
> testing/marionette/harness -> marionette-client

As you can see we will fix one part only because we cannot rename
marionette-driver to marionette-client now. We may consider to do so for
Firefox 59 which is the overnext ESR release. But the changes for the
harness package will definitely also land for the 52 ESR release and as
such will be uplifted to mozilla-aurora soon.

What does it mean for you?
-------------------------------------

If your code is located in in the tree you don't have to do anything. My
patch will update every single instance where the old package name was used.

For external code you will have to update your package dependencies once
the code has been landed and the new package released to PyPI. If you
don't do so, no further updates will be available via PyPI.

In case you have questions please let us know.

Thanks,

--
Henrik Skupin
Senior Software Engineer
Mozilla Corporation

[Xidorn Quan]

Note that this kind of changes may lead to weird Python error. We have
seen one in bug 1321468.

If you recently see any unexpected Python error when running mach
commands, try execute "./mach clobber python" first. ("./mach clobber"
would *not* work because it only purges things inside the objdir, no
*.pyc files elsewhere.)

- Xidorn

> _______________________________________________
> dev-platform mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform

[Henrik Skupin]

Xidorn Quan wrote on 02/12/16 00:49:

> Note that this kind of changes may lead to weird Python error. We have
> seen one in bug 1321468.
>
> If you recently see any unexpected Python error when running mach
> commands, try execute "./mach clobber python" first. ("./mach clobber"
> would *not* work because it only purges things inside the objdir, no
> *.pyc files elsewhere.)

Thanks for following up on this topic! One thing I could suggest is to
simply get rid of the generation of .pyc files when running Python
commands. This can be done by exporting the following variable:

export PYTHONDONTWRITEBYTECODE=1

[Henrik Skupin]

Xidorn Quan wrote on 02/12/16 00:49:

> Note that this kind of changes may lead to weird Python error. We have
> seen one in bug 1321468.
>
> If you recently see any unexpected Python error when running mach
> commands, try execute "./mach clobber python" first. ("./mach clobber"
> would *not* work because it only purges things inside the objdir, no
> *.pyc files elsewhere.)

Thanks for following up on this topic! One thing I could suggest is to
simply get rid of the generation of .pyc files when running Python
commands. This can be done by exporting the following variable:

export PYTHONDONTWRITEBYTECODE=1