Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

Bug reports

When reporting a bug please include:

  • Your operating system name and version.
  • Any details about your local setup that might be helpful in troubleshooting.
  • Detailed steps to reproduce the bug.

Documentation improvements

The Open API Specifications Advanced Python Introspection library could always use more documentation, whether as part of the official The Open API Specifications Advanced Python Introspection library docs, in docstrings, or even on the web in blog posts, articles, and such.

Feature requests and feedback

The best way to send feedback is to file an issue at

If you are proposing a feature:

  • Explain in detail how it would work.
  • Keep the scope as narrow as possible, to make it easier to implement.
  • Remember that this is a volunteer-driven project, and that code contributions are welcome :)


To set up oasapi for local development:

  1. Fork oasapi (look for the “Fork” button).

  2. Clone your fork locally:

    git clone
  3. Create a branch for local development:

    git checkout -b name-of-your-bugfix-or-feature

    Now you can make your changes locally.

  4. When you’re done making changes run all the checks and docs builder with tox one command:

  5. Commit your changes and push your branch to GitHub:

    git add .
    git commit -m "Your detailed description of your changes."
    git push origin name-of-your-bugfix-or-feature
  6. Submit a pull request through the GitHub website.

Pull Request Guidelines

If you need some code review or feedback while you’re developing the code just make the pull request.

For merging, you should:

  1. Include passing tests (run tox) [1].
  2. Update documentation when there’s new API, functionality etc.
  3. Add a note to CHANGELOG.rst about the changes.
  4. Add yourself to AUTHORS.rst.

If you don’t have all the necessary python versions available locally you can rely on Travis - it will run the tests for each change you add in the pull request.

It will be slower though …


To install a minimal virtual environment with tox (see )

cd path-to-your-oasapi-folder
python -m venv .env
' activate your .env virtualenv
python -m pip install -r requirements-dev.txt

To install the git pre-commit scripts:

pre-commit install

To run the tests locally:

cd path-to-your-oasapi-folder
' activate your .env virtualenv

To build the documentation locally (available in the folder docs/dist, entry point docs/dist/index.html):

cd path-to-your-oasapi-folder
' activate your .env virtualenv
tox -e docs

To recreate the tox environments (e.g. if you add a dependency in the

tox --recreate
tox --recreate -e py36              '(only the py36 environment)

To run a subset of tests:

tox -e envname -- pytest -k test_myfeature

To run all the test environments in parallel (you need to pip install detox):


Tips with PyCharm

To run tox within PyCharm, right click on tox.ini and choose Run (see

Tips to deploy (for the maintainers)

To bump the version:

' update/commit first all your changes including the changelog
bump2version patch --tag --commit

To build the source distribution:

' clean first the /dist folder
python sdist

To upload on PyPI Test:

python -m twine upload --repository-url dist/*

To upload on PyPI:

python -m twine upload dist/*

For the setup of the deploy to PyPI step on Travis, the information on (with the online encrypt tool on were useful.