Description

This module can be used to build, handle, process and search tries

Interpreter

The package has been developed and tested with Python 2.7, 3.5, 3.6 and 3.7 under Linux (Debian, Ubuntu), Apple macOS and Microsoft Windows

Installing

$ pip install ptrie

Documentation

Available at Read the Docs

Contributing

1. Abide by the adopted code of conduct

2. Fork the repository from GitHub and then clone personal copy [1]:

   $ github_user=myname
   $ git clone --recurse-submodules \
         https://github.com/"${github_user}"/ptrie.git
   Cloning into 'ptrie'...
   ...
   $ cd ptrie || exit 1
   $ export PTRIE_DIR=${PWD}
   $

3. The package uses two sub-modules: a set of custom Pylint plugins to help with some areas of code quality and consistency (under the pylint_plugins directory), and a lightweight package management framework (under the pypkg directory). Additionally, the pre-commit framework is used to perform various pre-commit code quality and consistency checks. To enable the pre-commit hooks:

   $ cd "${PTRIE_DIR}" || exit 1
   $ pre-commit install
   pre-commit installed at .../ptrie/.git/hooks/pre-commit
   $

4. Ensure that the Python interpreter can find the package modules (update the $PYTHONPATH environment variable, or use sys.paths(), etc.)

   $ export PYTHONPATH=${PYTHONPATH}:${PTRIE_DIR}
   $

5. Install the dependencies (if needed, done automatically by pip):

   • Cog (2.5.1 or newer)
   • Coverage (4.5.3 or newer)
   • Docutils (0.14 or newer)
   • Inline Syntax Highlight Sphinx Extension (0.2 or newer)
   • Mock (2.0.0 or newer)
   • Pmisc (1.5.8 or newer)
   • Py.test (4.3.1 or newer)
   • Pydocstyle (3.0.0 or newer)
   • Pylint (Python 2.x: 1.9.4 or newer, Python 3.x: 2.3.1 or newer)
   • Pytest-coverage (2.6.1 or newer)
   • Pytest-pmisc (1.0.7 or newer)
   • Pytest-xdist (optional, 1.26.0 or newer)
   • ReadTheDocs Sphinx theme (0.4.3 or newer)
   • Shellcheck Linter Sphinx Extension (1.0.8 or newer)
   • Sphinx (1.8.5 or newer)
   • Tox (3.7.0 or newer)
   • Virtualenv (16.4.3 or newer)

6. Implement a new feature or fix a bug

7. Write a unit test which shows that the contributed code works as expected. Run the package tests to ensure that the bug fix or new feature does not have adverse side effects. If possible achieve 100% code and branch coverage of the contribution. Thorough package validation can be done via Tox and Pytest:

   $ PKG_NAME=ptrie tox
   GLOB sdist-make: .../ptrie/setup.py
   py27-pkg create: .../ptrie/.tox/py27
   py27-pkg installdeps: -r.../ptrie/requirements/tests_py27.pip, -r.../ptrie/requirements/docs_py27.pip
   ...
     py27-pkg: commands succeeded
     py35-pkg: commands succeeded
     py36-pkg: commands succeeded
     py37-pkg: commands succeeded
     congratulations :)
   $

   Setuptools can also be used (Tox is configured as its virtual environment manager):

   $ PKG_NAME=ptrie python setup.py tests
   running tests
   running egg_info
   writing ptrie.egg-info/PKG-INFO
   writing dependency_links to ptrie.egg-info/dependency_links.txt
   writing requirements to ptrie.egg-info/requires.txt
   ...
     py27-pkg: commands succeeded
     py35-pkg: commands succeeded
     py36-pkg: commands succeeded
     py37-pkg: commands succeeded
     congratulations :)
   $

   Tox (or Setuptools via Tox) runs with the following default environments: py27-pkg, py35-pkg, py36-pkg and py37-pkg [3]. These use the 2.7, 3.5, 3.6 and 3.7 interpreters, respectively, to test all code in the documentation (both in Sphinx *.rst source files and in docstrings), run all unit tests, measure test coverage and re-build the exceptions documentation. To pass arguments to Pytest (the test runner) use a double dash (--) after all the Tox arguments, for example:

   $ PKG_NAME=ptrie tox -e py27-pkg -- -n 4
   GLOB sdist-make: .../ptrie/setup.py
   py27-pkg inst-nodeps: .../ptrie/.tox/.tmp/package/1/ptrie-1.1.7.zip
   ...
     py27-pkg: commands succeeded
     congratulations :)
   $

   Or use the -a Setuptools optional argument followed by a quoted string with the arguments for Pytest. For example:

   $ PKG_NAME=ptrie python setup.py tests -a "-e py27-pkg -- -n 4"
   running tests
   ...
     py27-pkg: commands succeeded
     congratulations :)
   $

   There are other convenience environments defined for Tox [3]:

   • py27-repl, py35-repl, py36-repl and py37-repl run the Python 2.7, 3.5, 3.6 and 3.7 REPL, respectively, in the appropriate virtual environment. The ptrie package is pip-installed by Tox when the environments are created. Arguments to the interpreter can be passed in the command line after a double dash (--).

   • py27-test, py35-test, py36-test and py37-test run Pytest using the Python 2.7, 3.5, 3.6 and 3.7 interpreter, respectively, in the appropriate virtual environment. Arguments to pytest can be passed in the command line after a double dash (--) , for example:

     $ PKG_NAME=ptrie tox -e py27-test -- -x test_ptrie.py
     GLOB sdist-make: .../ptrie/setup.py
     py27-pkg inst-nodeps: .../ptrie/.tox/.tmp/package/1/ptrie-1.1.7.zip
     ...
       py27-pkg: commands succeeded
       congratulations :)
     $

   • py27-test, py35-test, py36-test and py37-test test code and branch coverage using the 2.7, 3.5, 3.6 and 3.7 interpreter, respectively, in the appropriate virtual environment. Arguments to pytest can be passed in the command line after a double dash (--). The report can be found in ${PTRIE_DIR}/.tox/py[PV]/usr/share/ptr ie/tests/htmlcov/index.html where [PV] stands for 2.7, 3.5, 3.6 or 3.7 depending on the interpreter used.

8. Verify that continuous integration tests pass. The package has continuous integration configured for Linux, Apple macOS and Microsoft Windows (all via Azure DevOps).

9. Document the new feature or bug fix (if needed). The script ${PTRIE_DIR}/pypkg/build_docs.py re-builds the whole package documentation (re-generates images, cogs source files, etc.):

   $ "${PTRIE_DIR}"/pypkg/build_docs.py -h
   usage: build_docs.py [-h] [-d DIRECTORY] [-r]
                        [-n NUM_CPUS] [-t]
   
   Build ptrie package documentation
   
   optional arguments:
     -h, --help            show this help message and exit
     -d DIRECTORY, --directory DIRECTORY
                           specify source file directory
                           (default ../ptrie)
     -r, --rebuild         rebuild exceptions documentation.
                           If no module name is given all
                           modules with auto-generated
                           exceptions documentation are
                           rebuilt
     -n NUM_CPUS, --num-cpus NUM_CPUS
                           number of CPUs to use (default: 1)
     -t, --test            diff original and rebuilt file(s)
                           (exit code 0 indicates file(s) are
                           identical, exit code 1 indicates
                           file(s) are different)

Footnotes

[1]	All examples are for the bash shell

[2]	It is assumed that all the Python interpreters are in the executables path. Source code for the interpreters can be downloaded from Python's main site

[3]	(1, 2) Tox configuration largely inspired by Ionel's codelog

License

The MIT License (MIT)

Copyright (c) 2013-2019 Pablo Acosta-Serafini

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.