зеркало из https://github.com/mozilla/gecko-dev.git
df45b126d1
Did you know that our version of requests was from 2015? Phwoar! This bumps `jinja2`, `py`, `pyyaml`, `requests` and `urllib3`. There's significant risk for regressions due to breaking changes, though due to the dynamic nature of Python, they're tricky to track down. The potential breaking changes I'm expecting to potentially affect us are: * `requests@2.11.0`: No longer accepts non-strings as header values. * `requests@2.16.0`: `requests.packages` namespace was removed due to packages no longer being vendored. The namespace has been incrementally restored over future releases, but it's unclear to what degree. * `requests@2.24.0`: Redirect resolution now only happens when `allow_redirects` is `True`. * `requests` version of `urllib3` was bumped from `1.13.1` to `1.26`, unsure what repercussions that will have. This also added dependencies to `flake8_requirements`. This is because the vendored `importlib-metadata` update (and the new `typing-extensions` dependency) is found by `pip`, but the vendored `typing-extensions` is _not_ discovered (perhaps due to details around "eggs" and the way we add vendored code to the sys.path). So, `pip` tries to install it manually and fails when it finds no hash. By re-compiling `flake8_requirements`, the necessary hashes are made available. Differential Revision: https://phabricator.services.mozilla.com/D108526 |
||
|---|---|---|
| .. | ||
| examples | ||
| lib | ||
| lib3 | ||
| yaml | ||
| CHANGES | ||
| LICENSE | ||
| MANIFEST.in | ||
| Makefile | ||
| PKG-INFO | ||
| README | ||
| pyproject.toml | ||
| setup.cfg | ||
| setup.py | ||
README
PyYAML - The next generation YAML parser and emitter for Python.
To install, type 'python setup.py install'.
By default, the setup.py script checks whether LibYAML is installed
and if so, builds and installs LibYAML bindings. To skip the check
and force installation of LibYAML bindings, use the option '--with-libyaml':
'python setup.py --with-libyaml install'. To disable the check and
skip building and installing LibYAML bindings, use '--without-libyaml':
'python setup.py --without-libyaml install'.
When LibYAML bindings are installed, you may use fast LibYAML-based
parser and emitter as follows:
>>> yaml.load(stream, Loader=yaml.CLoader)
>>> yaml.dump(data, Dumper=yaml.CDumper)
If you don't trust the input stream, you should use:
>>> yaml.safe_load(stream)
PyYAML includes a comprehensive test suite. To run the tests,
type 'python setup.py test'.
For more information, check the PyYAML homepage:
'https://github.com/yaml/pyyaml'.
For PyYAML tutorial and reference, see:
'http://pyyaml.org/wiki/PyYAMLDocumentation'.
Discuss PyYAML with the maintainers in IRC #pyyaml irc.freenode.net.
You may also use the YAML-Core mailing list:
'http://lists.sourceforge.net/lists/listinfo/yaml-core'.
Submit bug reports and feature requests to the PyYAML bug tracker:
'https://github.com/yaml/pyyaml/issues'.
The PyYAML module was written by Kirill Simonov <xi@resolvent.net>.
It is currently maintained by the YAML and Python communities.
PyYAML is released under the MIT license.
See the file LICENSE for more details.