txwebbackendbase 0.0.2

Features

• TODO

Usage

• TODO

Note: See pipenv documentation for Pipfile specification.

Contributing

Create your environment with

$ pipenv --three

PS: you can use pipenv –two for Python 2.

Setup for development and unit tests:

$ pipenv install --dev

Note

Setup for production can be done with:

$ pipenv install

But if your application uses this library through a requirements.txt (Pip) or through a Pipfile (Pipenv), you should not have to do this “setup for production” command.

Activate the environment:

$ pipenv shell

Execute a command directly inside the environment:

$ pipenv run ...

Execute unit tests:

$ pipenv run pytest test

Build source package:

Use it for most package without low level system dependencies.

pipenv run python setup.py sdist

Build binary package:

Needed for package with a C or other low level source code.

pipenv run python setup.py bdist

Build Wheel package:

Always provide a wheel package.

pipenv run python setup.py bdist_wheel

(Only for package owner)

Register and publish your package to Pypi:

Do it locally only once, to create your package on pypi.python.org.

pipenv run python setup.py sdist register upload

Create a release:

Go on GitHub and create a tag with a semver syntax. Optionally you can tag code locally and push to GitHub.

git tag 1.2.3

On successful travis build on the Tag branch, your Pypi package will be updated automatically.