зеркало из https://github.com/mozilla/gecko-dev.git
dba3191147
There is probably a way to dynamically retrieve the version. But rather than take the chance we'd query the wrong thing, let's just parse the version that Visual Studio writes to the solution file when saving it and use it. With this change, generating the VisualStudio build backend should not change any files unless the build config has changed. This means we can generate Visual Studio files at will without causing Visual Studio to complain about the solution and other files changing and needing reloading. MozReview-Commit-ID: 1udZ72SLEzP --HG-- extra : rebase_source : d15bff5b30a021dc1180e48fb7bb0d6c84871b69 |
||
---|---|---|
.. | ||
PyECC | ||
altgraph | ||
bitstring | ||
blessings | ||
compare-locales | ||
configobj | ||
eme | ||
futures | ||
jsmin | ||
lldbutils | ||
mach | ||
macholib | ||
mock-1.0.0 | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozversioncontrol/mozversioncontrol | ||
psutil | ||
pyasn1 | ||
pyasn1-modules | ||
pystache | ||
pyyaml | ||
redo | ||
requests | ||
rsa | ||
slugid | ||
virtualenv | ||
which | ||
README | ||
mach_commands.py | ||
moz.build |
README
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 ## pyyaml | pystache Used in taskcluster related mach commands to update download from github and remove .git and tests. Then run tests in taskcluster/tests/