Граф коммитов

7 Коммитов

Автор SHA1 Сообщение Дата
Mitchell Hentges dc2fa7819c Bug 1713610: Require PyPI-vendored packages be added to requirements.in r=ahal
`./mach vendor python <package>` was already adding its new package
to `requirements.txt`, so we were getting full resolver support, which
is good. However, it caused our `requirements.in` file to start
getting out-of-date, and therefore made it harder to identify the
top-level dependencies.

Arguably, we could have `./mach vendor python <package>` automatically
update `requirements.in`, too, but then we need to solve the edge cases,
such as "What if the package is already in `requirements.in`? What if
that existing item has a different version?"

The hardest part of updating `requirements.in` was finding it, so I've
also modified the `./mach vendor python` help text to make it more
identifiable.

Differential Revision: https://phabricator.services.mozilla.com/D116386
2021-06-10 19:19:06 +00:00
Dave Hunt 749eeb4b79 Bug 1490253 - Update documentation on vendoring Python packages based on switch to pip-tools; r=ahal
Differential Revision: https://phabricator.services.mozilla.com/D8205

--HG--
extra : moz-landing-system : lando
2018-10-15 13:36:30 +00:00
Dave Hunt 5152485bdc Bug 1346026 - Add ability to vendor Python modules using mach; r=ahal,erik,ted
To vendor a Python package, run ``mach vendor python [PACKAGE]``, where
``[PACKAGE]`` is one or more package names along with a version number in the
format ``pytest==3.5.1``. The package will be installed, transient dependencies
will be determined, and a ``requirements.txt`` file will be generated with the
full list of dependencies. The requirements file is then used with ``pip`` to
download and extract the source distributions of all packages into the
``third_party/python`` directory.

If you're familiar with ``Pipfile`` you can also directly modify this in the in
the top source directory and then run ``mach vendor python`` for your changes
to take effect. This allows advanced options such as specifying alternative
package indexed (see below), and
`PEP 508 specifiers <https://www.python.org/dev/peps/pep-0508/>`_.§

MozReview-Commit-ID: CRWoFamUy7V

--HG--
extra : rebase_source : e71ab6ecc74a168faa9df7cc4c2273cd8bf9e0d2
2018-05-09 16:11:40 +01:00
Dorel Luca d6a248d5cd Backed out 3 changesets (bug 1346026) for Bugzilla linting
Backed out changeset 95410b5cdecc (bug 1346026)
Backed out changeset 705e8cb185d4 (bug 1346026)
Backed out changeset f293475f462d (bug 1346026)
2018-05-23 19:42:13 +03:00
Dave Hunt 4f9d65989d Bug 1346026 - Add ability to vendor Python modules using mach; r=ahal,erik,ted
To vendor a Python package, run ``mach vendor python [PACKAGE]``, where
``[PACKAGE]`` is one or more package names along with a version number in the
format ``pytest==3.5.1``. The package will be installed, transient dependencies
will be determined, and a ``requirements.txt`` file will be generated with the
full list of dependencies. The requirements file is then used with ``pip`` to
download and extract the source distributions of all packages into the
``third_party/python`` directory.

If you're familiar with ``Pipfile`` you can also directly modify this in the in
the top source directory and then run ``mach vendor python`` for your changes
to take effect. This allows advanced options such as specifying alternative
package indexed (see below), and
`PEP 508 specifiers <https://www.python.org/dev/peps/pep-0508/>`_.§

MozReview-Commit-ID: CRWoFamUy7V

--HG--
extra : rebase_source : e71ab6ecc74a168faa9df7cc4c2273cd8bf9e0d2
2018-05-09 16:11:40 +01:00
Sylvestre Ledru aefcd1c84b Bug 1448934 - Fix some spelling mistakes in locales/en-US r=flod
MozReview-Commit-ID: vGVudVgB31

--HG--
extra : rebase_source : cdc39375a3485a3133878c4dbbffe60c0b26e917
2018-04-24 10:26:35 +02:00
Dave Hunt 4d1d1447df Bug 1447057 - Document policies for using third-party Python packages; r=gps
MozReview-Commit-ID: 8eJt84pEKlv

--HG--
extra : rebase_source : 88ff3693be50954f28bb9e5a46f412e8dd2432ff
2018-03-19 17:53:33 +00:00