zstd: vendor python-zstandard 0.5.0 As the commit message for the previous changeset says, we wish for zstd to be a 1st class citizen in Mercurial. To make that happen, we need to enable Python to talk to the zstd C API. And that requires bindings. This commit vendors a copy of existing Python bindings. Why do we need to vendor? As the commit message of the previous commit says, relying on systems in the wild to have the bindings or zstd present is a losing proposition. By distributing the zstd and bindings with Mercurial, we significantly increase our chances that zstd will work. Since zstd will deliver a better end-user experience by achieving better performance, this benefits our users. Another reason is that the Python bindings still aren't stable and the API is somewhat fluid. While Mercurial could be coded to target multiple versions of the Python bindings, it is safer to bundle an explicit, known working version. The added Python bindings are mostly a fully-featured interface to the zstd C API. They allow one-shot operations, streaming, reading and writing from objects implements the file object protocol, dictionary compression, control over low-level compression parameters, and more. The Python bindings work on Python 2.6, 2.7, and 3.3+ and have been tested on Linux and Windows. There are CFFI bindings, but they are lacking compared to the C extension. Upstream work will be needed before we can support zstd with PyPy. But it will be possible. The files added in this commit come from Git commit e637c1b214d5f869cf8116c550dcae23ec13b677 from https://github.com/indygreg/python-zstandard and are added without modifications. Some files from the upstream repository have been omitted, namely files related to continuous integration. In the spirit of full disclosure, I'm the maintainer of the "python-zstandard" project and have authored 100% of the code added in this commit. Unfortunately, the Python bindings have not been formally code reviewed by anyone. While I've tested much of the code thoroughly (I even have tests that fuzz APIs), there's a good chance there are bugs, memory leaks, not well thought out APIs, etc. If someone wants to review the code and send feedback to the GitHub project, it would be greatly appreciated. Despite my involvement with both projects, my opinions of code style differ from Mercurial's. The code in this commit introduces numerous code style violations in Mercurial's linters. So, the code is excluded from most lints. However, some violations I agree with. These have been added to the known violations ignore list for now.

     1

#require test-repo

     2

     3

  $ . "$TESTDIR/helpers-testrepo.sh"

     4

  $ check_code="$TESTDIR"/../contrib/check-code.py

     5

  $ cd "$TESTDIR"/..

     6

     7

New errors are not allowed. Warnings are strongly discouraged.

     8

(The writing "no-che?k-code" is for not skipping this file when checking.)

     9

    10

  $ hg locate -X contrib/python-zstandard | sed 's-\\-/-g' |

    11

  >   xargs "$check_code" --warnings --per-file=0 || false

    12

  Skipping hgext/fsmonitor/pywatchman/__init__.py it has no-che?k-code (glob)

    13

  Skipping hgext/fsmonitor/pywatchman/bser.c it has no-che?k-code (glob)

    14

  Skipping hgext/fsmonitor/pywatchman/capabilities.py it has no-che?k-code (glob)

    15

  Skipping hgext/fsmonitor/pywatchman/msc_stdint.h it has no-che?k-code (glob)

    16

  Skipping hgext/fsmonitor/pywatchman/pybser.py it has no-che?k-code (glob)

    17

  Skipping i18n/polib.py it has no-che?k-code (glob)

    18

  Skipping mercurial/httpclient/__init__.py it has no-che?k-code (glob)

    19

  Skipping mercurial/httpclient/_readers.py it has no-che?k-code (glob)

    20

  Skipping mercurial/statprof.py it has no-che?k-code (glob)