зеркало из https://github.com/mozilla/gecko-dev.git
35b16fdf28
The `mozbase` modules were being unconditionally added to the `sys.path` regardless of the Mach command being run, so there isn't much value keeping them in a separate file. Besides, all other source module paths are described in `common_virtualenv_packages`, why is `mozbase` special? In the future, we're going to want to make improvements here (such as: there's a difference between informing mach of first-party code versus defining which third_party vendored packages should be in scope, and that workflow difference should be represented in-code). It's useful to peel out the existing, less useful abstraction before we can build a stronger one. Differential Revision: https://phabricator.services.mozilla.com/D117711 |
||
---|---|---|
.. | ||
docs | ||
manifestparser | ||
mozcrash | ||
mozdebug | ||
mozdevice | ||
mozfile | ||
mozgeckoprofiler | ||
mozhttpd | ||
mozinfo | ||
mozinstall | ||
mozleak | ||
mozlog | ||
moznetwork | ||
mozpower | ||
mozprocess | ||
mozprofile | ||
mozproxy | ||
mozrunner | ||
mozscreenshot | ||
mozsystemmonitor | ||
moztest | ||
mozversion | ||
rust | ||
README.md | ||
moz.build | ||
setup_development.py | ||
versioninfo.py |
README.md
Mozbase
Mozbase is a set of easy-to-use Python packages forming a supplemental standard library for Mozilla. It provides consistency and reduces redundancy in automation and other system-level software. All of Mozilla's test harnesses use mozbase to some degree, including Talos, mochitest, and reftest.
Learn more about mozbase at the project page.
Read detailed docs online, or build them locally by running "make html" in the docs directory.