Convenient tools for using Swagger to define and validate your interfaces in a Pyramid webapp.
Clone or download
striglia Add Appveyor badge to readme
Windows-CI tool (like travis). See https://ci.appveyor.com/project/striglia/pyramid-swagger for current status.
Latest commit 1dbc0b4 Jul 6, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs
pyramid_swagger
tests Fix schema_url generation broken on Windows Jun 30, 2018
.activate.sh
.appveyor.yml Add appveyor testing configuration Jun 27, 2018
.deactivate.sh
.gitignore
.landscape.yaml
.pre-commit-config.yaml
.travis.yml
LICENSE
MANIFEST.in
Makefile
README.rst
requirements-dev.txt Add pre-commit, virtual environment, requirements-dev.txt Mar 9, 2017
setup.cfg
setup.py
tox.ini

README.rst

PyPI:https://pypi.python.org/pypi/pyramid_swagger
Documentation:http://pyramid-swagger.readthedocs.org/en/latest/
Source:https://github.com/striglia/pyramid_swagger
License:Copyright © 2014 Scott Triglia under the BSD 3-clause
Build status:Travis CI Appveyor (Windows CI)
Current coverage on master:https://coveralls.io/repos/striglia/pyramid_swagger/badge.png
Persistent chat for questions:Join the chat at https://gitter.im/striglia/pyramid_swagger

pyramid_swagger

This project offers convenient tools for using Swagger to define and validate your interfaces in a Pyramid webapp.

Full documentation is available at http://pyramid-swagger.readthedocs.org/.

How to contribute

  1. Fork this repository on Github: https://help.github.com/articles/fork-a-repo/

  2. Clone your forked repository: https://help.github.com/articles/cloning-a-repository/

  3. Make a feature branch for your changes:

    git remote add upstream https://github.com/striglia/pyramid_swagger.git
    git fetch upstream
    git checkout upstream/master -b my-feature-branch
    
  4. Create and activate the virtual environment, this will provide you with all the libraries and tools necessary for pyramid_swagger development:

    make
    source .activate.sh
    
  5. Make sure the test suite works before you start:

    tox -e py27    # Note: use py35 for Python 3.5, see tox.ini for possible values
    
  6. Commit patches: http://gitref.org/basic/

  7. Push to github: git pull && git push origin

  8. Send a pull request: https://help.github.com/articles/creating-a-pull-request/

Running a single test

Make sure you have activated the virtual environment (see above).

py.test -vvv tests/tween_test.py::test_response_properties