WARNING: This is from spyne's development branch. This version is not
released yet! Latest stable release can be found in the
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's home page is: http://spyne.io/
- The latest documentation for all releases of Spyne can be found at: http://spyne.io/docs
- The official source code repository is at: https://github.com/arskom/spyne
- The official spyne discussion forum is at: people at spyne dot io. Subscribe either via http://lists.spyne.io/listinfo/people or by sending an empty message to: people-subscribe at spyne dot io.
- You can download Spyne releases from Github or PyPi.
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
pytz is optional.
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.3 and up. You can track the Python 3 porting progress from our jenkins deployment, here: https://spyne.ci.cloudbees.com/job/spyne/PYFLAV=3.3/
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
- 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
- pyzmq is needed for
- Werkzeug is needed for using
spyne.protocol.http.HttpRpcunder a wsgi transport.
- PyParsing is needed for
- Twisted is needed for anything in
- Django (tested with 1.4 and up) is needed for
- Pyramid is needed for
- msgpack-python is needed for
- PyYaml is needed for
- simplejson is used when found
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 setup.py 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:
or you can clone the latest master tree from Github:
git clone git://github.com/arskom/spyne.git
To install from source distribution, you can run the setup script as usual:
python setup.py install [--user]
If you want to make any changes to the Spyne code, just use
python setup.py develop [--user]
so that you can painlessly test your patches.
Finally, to run the tests use:
pyhon setup.py 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.
The official mailing list for both users and developers alike can be found at: http://lists.spyne.io/listinfo/people.
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 the database that holds the most important information for the project, so we must avoid cluttering it as much as possible.
Please see the CONTRIBUTING.rst file in the Spyne source distribution for information about how you can help Spyne get more awesome.
Spyne committers get a free license for PyCharm Professional Edition, courtesy of JetBrains.
CloudBees generously hosts our Jenkins installation and gives us a ton of compute time for free.
Thanks a lot guys!..