About¶

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.

Spyne currently supports the WSDL 1.1 interface description standard, along with SOAP 1.1 and the so-called HttpRpc, XmlDocument, JsonDocument, YamlDocument, MessagePackDocument and MessagePackRpc protocols which can be transported via Http or ZeroMQ. The transports can be used in both a client or server setting.

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@spyne.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.

Requirements¶

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.

Installing¶

You can get spyne via pypi:

easy_install spyne

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.

Getting Support¶

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.

Contributing¶

Please see the CONTRIBUTING.rst file in the Spyne source distribution for information about how you can help Spyne get more awesome.

Acknowledgments¶

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!..