Dependency injection framework for Python
Go to file
2015-03-31 18:00:11 +03:00
examples Updating examples 2015-03-31 18:00:11 +03:00
objects Adding Objects introduction 2015-03-30 00:46:48 +03:00
tests Removing reduce function references from tests 2015-03-26 00:54:34 +02:00
.coveragerc adding .coveragerc and some tests 2015-03-10 16:12:42 +02:00
.gitignore Updating .gitignore 2015-03-27 01:28:40 +02:00
.pylintrc adding pylint settings file 2015-03-11 15:39:28 +02:00
.travis.yml Run tests on pypy and pypy3 2015-03-26 16:56:49 +02:00
LICENSE 0.4.3 release 2015-03-08 00:26:44 +02:00
manage.py Removing of old check function from manage.py 2015-03-23 16:40:59 +02:00
MANIFEST.in renaming manifest file, 0.0.6 2015-01-16 23:11:24 +02:00
README.md Updating examples 2015-03-31 18:00:11 +03:00
requirements-maintain.txt adding pep257, flake8 and pylint libs to requirements 2015-03-09 00:02:20 +02:00
requirements.txt adding six to requirements 2015-01-05 11:38:33 +02:00
setup.py Adding Objects introduction 2015-03-30 00:46:48 +03:00
tox.ini Run tests on pypy and pypy3 2015-03-26 16:56:49 +02:00
VERSION 0.6.2 release 2015-03-26 17:28:12 +02:00

Objects

Dependency management tool for Python projects.

Latest Version Downloads Build Status Coverage Status License Supported Python versions Supported Python implementations

Introduction

Python ecosystem consists of a big amount of various classes, functions and objects that could be used for applications development. Each of them has its own role.

Modern Python applications are mostly the composition of well-known open source systems, frameworks, libraries and some turnkey functionality.

When application goes bigger, its amount of objects and their dependencies also increased extremely fast and became hard to maintain.

Objects is designed to be developer's friendly tool for managing objects and their dependencies in formal, pretty way. Main idea of Objects is to keep dependencies under control.

Entities

Current section describes main Objects entities and their interaction.

Providers

Providers are strategies of accessing objects.

All providers are callable. They describe how particular objects will be provided. For example:

"""`NewInstance` and `Singleton` providers example."""

from objects.providers import NewInstance
from objects.providers import Singleton


# NewInstance provider will create new instance of specified class
# on every call.
new_object = NewInstance(object)

object_1 = new_object()
object_2 = new_object()

assert object_1 is not object_2

# Singleton provider will create new instance of specified class on first call,
# and return same instance on every next call.
single_object = Singleton(object)

single_object_1 = single_object()
single_object_2 = single_object()

assert single_object_1 is single_object_2

Injections

Injections are additional instructions, that are used for determining dependencies of objects.

Objects can take dependencies in various forms. Some objects take init arguments, other are using attributes or methods to be initialized. Injection, in terms of Objects, is an instruction how to provide dependency for the particular object.

Every Python object could be an injection's value. Special case is a Objects provider as an injection's value. In such case, injection value is a result of injectable provider call (every time injection is done).

Injections are used by providers.

"""`KwArg` and `Attribute` injections example."""

import sqlite3

from objects.providers import Singleton
from objects.providers import NewInstance

from objects.injections import KwArg
from objects.injections import Attribute


class ObjectA(object):

    """ObjectA has dependency on database."""

    def __init__(self, database):
        """Initializer.

        Database dependency need to be injected via init arg."""
        self.database = database

    def get_one(self):
        """Select one from database and return it."""
        return self.database.execute('SELECT 1').fetchone()[0]


# Database and `ObjectA` providers.
database = Singleton(sqlite3.Connection,
                     KwArg('database', ':memory:'),
                     KwArg('timeout', 30),
                     KwArg('detect_types', True),
                     KwArg('isolation_level', 'EXCLUSIVE'),
                     Attribute('row_factory', sqlite3.Row))

object_a = NewInstance(ObjectA,
                       KwArg('database', database))

# Creating several `ObjectA` instances.
object_a_1 = object_a()
object_a_2 = object_a()

# Making some asserts.
assert object_a_1 is not object_a_2
assert object_a_1.database is object_a_2.database
assert object_a_1.get_one() == object_a_2.get_one() == 1

Catalogs

Catalogs are named set of providers.

Advanced usage

Below you can find some variants of advanced usage of Objects.

Inject decorator

@inject decorator could be used for patching any callable with injection. Any Python object will be injected 'as is', except Objects providers, that will be called to provide injectable value.

"""`@inject` decorator example."""

from objects.providers import NewInstance

from objects.injections import KwArg
from objects.injections import inject


new_object = NewInstance(object)


@inject(KwArg('object_a', new_object))
@inject(KwArg('some_setting', 1334))
def example_callback(object_a, some_setting):
    """This function has dependencies on object a and b.

    Dependencies are injected using `@inject` decorator.
    """
    assert isinstance(object_a, object)
    assert some_setting == 1334


example_callback()
example_callback()

Overriding providers

Overriding catalogs