зеркало из https://github.com/mozilla/gecko-dev.git
dc2fa7819c
`./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 |
||
---|---|---|
.. | ||
index.rst |