Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Dependency Injection Container for Python 3+. Uses Python 3 annotations to provide hints for the components that should be injected.
Dependency Injection Container for Python 3+ influenced partially by Autofac_. dic aims to be a tiny "out of the way" framework to help realise IoC via dependency injection. dic uses Python 3 annotations to provide hints for the components that should be injected.
|version| |build| |docs|
dic documentation is available via Read the Docs
_.
dic is available via pip: ::
pip install dic
Currently, dic supports:
A quick example on how to use dic: ::
import dic
class SimpleThing(object):
def say(self, message):
print(message)
class RequiresThing(object):
def __init__(self, thing: SimpleThing):
self.thing = thing
def say(self, message):
self.thing.say(message)
# build the container
builder = dic.container.ContainerBuilder()
builder.register_class(SimpleThing)
builder.register_class(RequiresThing, component_scope=dic.scope.SingleInstance)
container = builder.build()
# use the container
# Note there'll only be one of these due to SingleInstance scoping during build
x = container.resolve(RequiresThing)
x.say("my message")
dic supports basic relationships:
dic.rel.Lazy
- don't create the dependency until it's first useddic.rel.Factory
- the component wants to create other components. Lifetime scopes are respected. Supports custom arguments.Using a factory: ::
import dic
class SimpleThing(object):
def __init__(self, special_argument):
self.special_argument = special_argument
class BuildsThings(object):
def __init__(self, thing_factory: dic.rel.Factory(SimpleThing)):
self.thing_factory = thing_factory
def build_me_a_thing(self):
# builds a new thing using the injected factory
# Note that custom arguments can be provided here
self.thing_factory(special_argument="My super special argument")
# build the container
builder = dic.container.ContainerBuilder()
builder.register_class(SimpleThing)
builder.register_class(BuildsThing)
container = builder.build()
# use the container
x = container.resolve(BuildsThing)
# use it
thing = x.build_me_a_thing()
# ...
Yes. dic.rel.Lazy
and dic.container.Container.resolve()
are thread-safe. As a result, do not store the component_context given to register_callback
callbacks,
as thread-safety is enforced at the container.resolve() level.
Yes. Derive a scope from dic.scope.Scope
. Scopes can be used to provide lifetime for a calling thread, for example
.. _Autofac: http://autofac.org/
.. _Read the Docs
: http://dic.readthedocs.org/
.. |version| image:: https://pypip.in/version/dic/badge.svg?text=version
:target: https://pypi.python.org/pypi/dic
.. |docs| image:: https://readthedocs.org/projects/dic/badge/?version=latest
:target: https://readthedocs.org/projects/dic/
.. |build| image:: https://travis-ci.org/zsims/dic.svg?branch=master
:target: https://travis-ci.org/zsims/dic
FAQs
Dependency Injection Container for Python 3+. Uses Python 3 annotations to provide hints for the components that should be injected.
We found that dic demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.