gecko-dev/python
Gregory Szorc 177461528f Bug 687388 - Visual Studio project generation; r=mshal
A new moz.build-based build backend for Visual Studio project generation
has been added. The build backend can be used by specifying
'VisualStudio' to the backend option of config.status or mach
build-backend. e.g. `mach build-backend -b VisualStudio`.

Usage docs have been added to build/docs/visualstudio.rst.

--HG--
extra : rebase_source : dfb5c43a22434600c5bb4870ec5be2f39b4820e9
extra : amend_source : f1000754400f280778a669b8c34d90c5ef95d966
2014-02-14 16:31:14 -08:00
..
blessings
codegen Bug 462463 - Stop using mddepend.pl. r=ted 2013-04-09 15:10:25 -07:00
configobj Bug 894227 - Add configobj Python package; rs=glandium 2013-07-18 12:55:41 -07:00
lldbutils Fix error in lldb string serialiation; no bug. (DONTBUILD, NPOTB) 2014-02-17 15:22:59 +11:00
mach Bug 909522 - Run mach's unit tests as part of make check; r=mshal 2014-01-09 11:20:41 -08:00
mock-1.0.0 Merge the last PGO-green inbound changeset to m-c. 2012-11-07 20:08:02 -05:00
mozboot Bug 950107 - Support ALL_PROXY in bootstraper; r=gps 2014-02-05 13:10:00 -08:00
mozbuild Bug 687388 - Visual Studio project generation; r=mshal 2014-02-14 16:31:14 -08:00
mozversioncontrol/mozversioncontrol Bug 941833 - mach mercurial-setup should define host fingerprints during repo operations; r=nalexander 2013-11-21 12:19:32 -08:00
psutil Bug 908296 - Upgrade psutil to version 1.0.1; rs=glandium 2013-08-23 10:18:57 -07:00
virtualenv Bug 914500 - Upgrade virtualenv to 1.10.1; r=mshal 2013-09-10 17:07:12 -07:00
which Bug 792135 - Part 1: Add which Python package; r=glandium 2012-09-20 20:54:46 -07:00
Makefile.in Bug 909522 - Run mach's unit tests as part of make check; r=mshal 2014-01-09 11:20:41 -08:00
README
mach_commands.py Bug 952280 - mach python commands now use virtualenv APIs; r=mshal 2013-12-19 13:48:37 -08:00
moz.build Bug 939367 - Allow Sphinx docs to come from all over the tree; r=glandium 2013-11-20 12:37:22 -08:00

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