Skip to content
A transport and architecture agnostic RPC library that focuses on exposing services with a well-defined API using popular protocols.
Branch: master
Clone or download
Latest commit d64f971 Feb 18, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
doc Fix typo in docs. fixes #549 Mar 31, 2018
examples use spyne.Application instead of neurons.daemon.HttpApplications Feb 19, 2019
requirements test with latest sqlalchemy Feb 18, 2019
spyne verbump Feb 19, 2019
.landscape.yaml add config file for Jan 28, 2015
.travis.yml add python 3.7 compat sigils Apr 12, 2018
CHANGELOG.rst changelog update Dec 20, 2018
CONTRIBUTING.rst tweaks to the CONTRIBUTING file Aug 29, 2018
LICENSE add license for django-ipware Feb 27, 2017

README.rst Code Health

WARNING: This is from spyne's development branch. This version is not released yet! Latest stable release can be found in the 2_12 branch.

If you like and use Spyne, star it on Github!


Spyne aims to save the protocol implementers the hassle of implementing their own remote procedure call api and the application programmers the hassle of jumping through hoops just to expose their services using multiple protocols and transports.

In other words, Spyne is a framework for building distributed solutions that strictly follow the MVC pattern, where Model = spyne.model, View = spyne.protocol and Controller = user code.

Spyne comes with the implementations of popular transport, protocol and interface document standards along with a well-defined API that lets you build on existing functionality.

The following are the primary sources of information about spyne:


Spyne source distribution is a collection of highly decoupled components, which makes it a bit difficult to put a simple list of requirements, as literally everything except pytz is optional.

Python version

First things first: Spyne is known to fully work on Python versions 2.6 and 2.7. However Spyne's Soap (and all of its subcomponents like XmlDocument, Wsdl, etc.) subsystem also works on Python 3.4 and up. You can track the Python 3 porting progress from our jenkins deployment, here:

The only hard requirement is pytz which is available via PyPi.


Additionally the following software packages are needed for various subsystems of Spyne:

  • A Wsgi server of your choice is needed to wrap spyne.server.wsgi.WsgiApplication
  • lxml>=3.2.5 is needed for any xml-related protocol.
  • lxml>=3.4.1 is needed for any html-related protocol.
  • SQLAlchemy is needed for spyne.model.complex.TTableModel.
  • pyzmq is needed for spyne.client.zeromq.ZeroMQClient and spyne.server.zeromq.ZeroMQServer.
  • Werkzeug is needed for using spyne.protocol.http.HttpRpc under a wsgi transport.
  • PyParsing is needed for using HttpPattern's with spyne.protocol.http.HttpRpc.
  • Twisted is needed for anything in spyne.server.twisted and spyne.client.twisted.
  • Django (tested with 1.8 and up) is needed for anything in spyne.server.django.
  • Pyramid is needed for spyne.server.pyramid.PyramidApplication.
  • msgpack-python is needed for spyne.protocol.msgpack.
  • PyYaml is needed for spyne.protocol.yaml.
  • simplejson is used when found for spyne.protocol.json.

You are advised to add these as requirements to your own projects, as these are only optional dependencies of Spyne, thus not handled in its setup script.


You first need to have package manager (pip, easy_install) installed. Spyne ships with a setuptools bootstrapper, so if refuses to run because it can't find setuptools, do:


You can add append --user to get it installed with $HOME/.local prefix.

You can get spyne via pypi:

easy_install [--user] spyne

or you can clone the latest master tree from Github:

git clone git://

To install from source distribution, you can run the setup script as usual:

python install [--user]

If you want to make any changes to the Spyne code, just use

python develop [--user]

so that you can painlessly test your patches.

Finally, to run the tests use:

python test

The test script should first install every single library that Spyne integrates with to the current directory, along with additional packages like pytest or tox that are only needed when running Spyne testsuite.

Getting Support

The official mailing list for both users and developers alike can be found at:

You can also use the 'spyne' tag to ask questions on Stack Overflow.

Please don't use the issue tracker for asking questions. It's a database that holds the most important information for the project, so we must avoid cluttering it as much as possible.


If you feel like helping out, see the CONTRIBUTING.rst file in the Spyne source distribution for starting points and general guidelines.

You can’t perform that action at this time.