gecko-dev/python
Tom Ritter 83f834aede Bug 1392643 Turn on c++14 for MinGW globally r=bagder,froydnj
Technically this turns on gnu++14. I encountered a few errors when using c++14:
1) _USE_MATH_DEFINES needed to be defined for MinGW
2) MinGW did not define _finite under c++14
3) MinGW's float.h did not define Microsoft specific float functions under c++14

All of these were because c++14 defines _STRICT_ANSI_ which MinGW obeys and
avoids defining certain functions. The first two could be patched around, but
the third was a blocker, so we switched to gnu++14

MozReview-Commit-ID: 6Y7gEQgApYp

--HG--
extra : rebase_source : dabbd40c049c36e780b585e0bef0a8e25887d089
2017-09-22 12:26:42 -05:00
..
devtools/migrate-l10n
mach Bug 1399989 - Add python/mach to flake8 linter. r=gps 2017-09-17 22:41:17 -04:00
mozboot Bug 1401166 - Skip Stylo dependency with ./mach bootstrap on OpenBSD. r=rillian f=gaston 2017-09-19 12:19:40 +00:00
mozbuild Bug 1392643 Turn on c++14 for MinGW globally r=bagder,froydnj 2017-09-22 12:26:42 -05:00
mozlint Bug 1392787 - [mozlint] Fix bugs in path filtering and add a test, r=jmaher 2017-08-23 06:33:06 -04:00
mozversioncontrol/mozversioncontrol Bug 1397406 - Add Repository method to determine if working directory clean; r=dustin 2017-09-06 12:15:12 -07:00
mach_commands.py Bug 1339178 - Use pytest to run python-tests, r=davehunt 2017-08-29 14:50:33 -04:00
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:

* Vendored python modules (use third_party/python instead)
* 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
https://bugzilla.mozilla.org/show_bug.cgi?id=1346025