gitter-badger / ipopo Goto Github PK

iPOPO: A component model for Python

iPOPO is a Python-based Service-Oriented Component Model (SOCM) based on Pelix, a dynamic service platform. They are inspired on two popular Java technologies for the development of long-lived applications: the iPOJO component model and the OSGi Service Platform. iPOPO enables to conceive long-running and modular IT services.

See https://ipopo.coderxpress.net for documentation and more information.

iPOPO is available on PyPI and is released under the terms of the Apache License 2.0.

Feedback

Feel free to send feedback on your experience of Pelix/iPOPO, via the mailing lists :

• User list: http://groups.google.com/group/ipopo-users (don't be shy)
• Development list: http://groups.google.com/group/ipopo-dev

Bugs and features requests can be submitted on GitHub tcalmant/ipopo.

More information at https://ipopo.coderxpress.net/

Compatibility

Pelix and iPOPO are tested using Tox and Travis-CI with Pypy 2.5.0 and Python 2.7, 3.2, 3.3 and 3.4.

Most of the framework can work with Python 2.6 if the importlib package is installed, but there is no guarantee that the latest features will be compatible.

Release notes: 0.6.1

See the CHANGELOG.rst file to see what changed in previous releases.

iPOPO

• The stack trace of the exception that caused a component to be in the ERRONEOUS state is now kept, as a string. It can be seen throught the instance shell command.

Shell

• The command parser has been separated from the shell core service. This allows to create custom shells without giving access to Pelix administration commands.
• Added cd and pwd shell commands, which allow changing the working directory of the framework and printing the current one.
• Corrected the encoding of the shell output string, to avoid exceptions when printing special characters.

Remote Services

• Corrected a bug where an imported service with the same endpoint name as an exported service could be exported after the unregistration of the latter.