Hello, I'm happy to announce that iPOPO v0.8.1 has just been released! What is iPOPO ============= iPOPO is a Service-Oriented Component Model (SOCM) based on Pelix, a dynamic service platform. Both 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. It is based on the concepts specified by OSGi: - Bundle: a Python module imported using Pelix and associated to a context. A bundle has a life-cycle (install, start, updated, stop, uninstall) - Service: a Python object registered in a service registry, associated to a specification and to properties. - Component: the instance of a class described/manipulated by iPOPO decorators Components are bound together by the specification(s) of the service(s) they provide. The required services are injected into components by iPOPO. For more information about those concepts, see https://ipopo.readthedocs.io/en/latest/refcards/index.html#refcards iPOPO provides many services out-of-the-box, like an HTTP server, local and remote shell, remote services... iPOPO is released under the terms of Apache Software License 2.0 What's new in 0.8.1 =================== This is bug fix release, for both the ThreadPool, used in Remote Services, and the RSA implementation: * Fixed a memory leak in the thread pool implementation. The patch comes from issue 35 of the jsonrpclib-pelix project. * Fixed a deadlock in the Py4J provider (issue #100), contributed by Scott Lewis. See pull request #101 for more details. You can take a look at the documentation at https://ipopo.readthedocs.io/ iPOPO is available on PyPI: https://pypi.python.org/pypi/iPOPO Source is available on GitHub: https://github.com/tcalmant/ipopo Feel free to send feedback on your experience of Pelix/iPOPO, via the mailing lists: User list : http://groups.google.com/group/ipopo-users Development list : http://groups.google.com/group/ipopo-dev Have fun!