Skip to content
Snippets Groups Projects
Commit dcad55f5 authored by Tom Teichler's avatar Tom Teichler :beers:
Browse files

New upstream version 0.2.1

parents
Branches
Tags upstream/0.2.1
No related merge requests found
Showing
with 1121 additions and 0 deletions
CHANGES 0 → 100644
Changelog
=========
0.2.1
*****
13/10/2014:
- Added tox to testing process (persisting theory is now tested under Python 2.7 and 3.4)
- Moved test directory outside of persisting-theory
- Set ``force_reload`` defaut to ``False`` to in Registry.autodiscover()
0.2.0
*****
26/07/2014:
- Added prepare_data hook for manipulating data before registration
- Added prepare_name hook for manipulating name before registration
- Added post_register hook
0.1.2
*****
13/07/2014:
- Added handling of error in autodiscovering
0.1.1
*****
12/07/2014:
- Added Python 3 support
0.1
***
12/07/2014 - initial release
\ No newline at end of file
COPYING 0 → 100644
Copyright (c) Eliot Berriot and individual contributors.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of persisting-theory nor the names of its contributors may be used
to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
include COPYING
include CHANGES
include README.rst
recursive-include example
\ No newline at end of file
PKG-INFO 0 → 100644
Metadata-Version: 1.1
Name: persisting-theory
Version: 0.2.1
Summary: Registries that can autodiscover values accross your project apps
Home-page: http://code.eliotberriot.com/eliotberriot/persisting-theory
Author: Eliot Berriot
Author-email: contact@eliotberriot.com
License: BSD
Description: Introduction
============
Persisting-theory is a small python utility designed to automate data discovering and access inside a list of packages. Use case: you are building an application that will have pluggable components. You want to allow these components to register data so it can be accessed by any other component of your app.
If you ever used Django framework, you may remember this::
from django.contrib import admin
admin.autodiscover()
Basically, persisting-theory will do the same, except that it let you declare what you want to autodiscover.
Okay, I'm bad at explaining things, and english is not my mother tongue. Let's build a simple example.
Quickstart
==========
Install
*******
Install the package from `PyPi <https://pypi.python.org/pypi/persisting-theory/>`_. via pip (or any other tool)::
pip install persisting-theory
Persisting-theory does not require any dependency but a python installation (it has been tested on python 2.7 and python 3.2).
Setup
*****
A basic setup::
# registries.py
from persiting_theory import Registry
class CallbacksRegistry(Registry):
"""
Allow your apps to register callbacks
"""
# the package where the registry will try to find callbacks in each app
look_into = "callbacks_registry"
callbacks_registry = CallbacksRegistry()
# app1/callbacks_registry.py
from registries import callbacks_registry
@callbacks_registry.register
def dog():
print("Wouf")
# app2/callbacks_registry.py
from registries import callbacks_registry
@callbacks_registry.register
def cat():
print("Meow")
# dosomething.py
from registries import callbacks_registry
APPS = (
'app1',
'app2',
)
# Trigger autodiscovering process
callbacks_registry.autodiscover(APPS)
for callback in callbacks_registry.values():
callback()
# Wouf
# Meow
API
===
``Registry`` inherits from python built-in `collections.OrderedDict`, which means you can use regular dict methods to access registered data::
callbacks_registry.get("dog")() # will print Wouf
assert callbacks_registry.get("chicken", None) is None
Registry.register()
*******************
You can use this function as a decorator for registering functions and classes::
from persisting_theory import Registry
class AwesomeRegistry(Registry):
pass
r = AwesomeRegistry()
# register a class
@r.register
class AwesomeClass:
pass
# register a function
@r.register
def awesome_function():
pass
# By default, the key in the registry for a given value is obtained from the function or class name, if possible
assert r.get("AwesomeClass") == AwesomeClass
assert r.get("awesome_function") == awesome_function
# You can override this behaviour:
@r.register(name="Chuck")
class AwesomeClass:
pass
@r.register(name="Norris")
def awesome_function():
pass
assert r.get("Chuck") == AwesomeClass
assert r.get("Norris") == awesome_function
# You can also use the register method as is
awesome_var = "Chuck Norris"
r.register(awesome_var, name="Who am I ?")
assert r.get("Who am I ?") == awesome_var
# I f you are not registering a function or a class, you MUST provide a name argument
Registry.validate()
*******************
By default, a registry will accept any registered value. Sometimes, it's not what you want, so you can restrict what kind of data your registry accepts::
from persisting_theory import Registry
class StartsWithAwesomeRegistry(Registry):
def validate(self, data):
if isinstance(data, str):
return data.startswith("awesome")
return False
r = StartsWithAwesomeRegistry()
# will pass registration
r.register("awesome day", name="awesome_day")
# will fail and raise ValueError
r.register("not so awesome day", name="not_so_awesome_day")
Registry.prepare_data()
***********************
If you want to manipulate your data before registering it, override this method. In this example, we prefix every registered string with 'hello'::
from persisting_theory import Registry
class HelloRegistry(Registry):
def prepare_data(self, data):
return 'hello ' + data
r = HelloRegistry()
class Greeting:
def __init__(self, first_name):
self.first_name = first_name
r.register(Greeting('World'), name="world")
r.register(Greeting('Eliot'), name="eliot")
assert r.register.get('world') == "hello World"
assert r.register.get('eliot') == "hello Eliot"
Registry.prepare_name()
***********************
In a similar way, you can manipulate the name of registered data. This can help if you want to avoid repetitions. Let's improve our previous example::
from persisting_theory import Registry
class HelloRegistry(Registry):
def prepare_data(self, data):
return 'hello ' + data
def prepare_name(self, data, name=None):
return self.data.first_name.lower()
r = HelloRegistry()
class Greeting:
def __init__(self, first_name):
self.first_name = first_name
r.register(Greeting('World'))
r.register(Greeting('Eliot'))
assert r.register.get('world') == "hello World"
assert r.register.get('eliot') == "hello Eliot"
Going meta
**********
If you have multiple registries, or want to allow your apps to declare their own registries, this is for you::
# registries.py
from persisting_theory import meta_registry, Registry
class RegistryA(Registry):
look_into = "a"
class RegistryB(Registry):
look_into = "b"
registry_a = RegistryA()
meta_registry.register(registry_a, name="registry_a")
registry_b = RegistryB()
meta_registry.register(registry_b, name="registry_b")
# dosomethingelse.py
from persisting_theory import meta_registry
# will import registries declared in `registries` packages, and trigger autodiscover() on each of them
meta_registry.autodiscover(apps=("app1", "app2"))
What the hell is that name ?
============================
It's an anagram for "python registries".
Contribute
==========
Contributions, bug reports, and "thank you" are welcomed. Feel free to contact me at <contact@eliotberriot.com>.
License
=======
The project is licensed under BSD licence.
Platform: UNKNOWN
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: BSD License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3.4
Introduction
============
Persisting-theory is a small python utility designed to automate data discovering and access inside a list of packages. Use case: you are building an application that will have pluggable components. You want to allow these components to register data so it can be accessed by any other component of your app.
If you ever used Django framework, you may remember this::
from django.contrib import admin
admin.autodiscover()
Basically, persisting-theory will do the same, except that it let you declare what you want to autodiscover.
Okay, I'm bad at explaining things, and english is not my mother tongue. Let's build a simple example.
Quickstart
==========
Install
*******
Install the package from `PyPi <https://pypi.python.org/pypi/persisting-theory/>`_. via pip (or any other tool)::
pip install persisting-theory
Persisting-theory does not require any dependency but a python installation (it has been tested on python 2.7 and python 3.2).
Setup
*****
A basic setup::
# registries.py
from persiting_theory import Registry
class CallbacksRegistry(Registry):
"""
Allow your apps to register callbacks
"""
# the package where the registry will try to find callbacks in each app
look_into = "callbacks_registry"
callbacks_registry = CallbacksRegistry()
# app1/callbacks_registry.py
from registries import callbacks_registry
@callbacks_registry.register
def dog():
print("Wouf")
# app2/callbacks_registry.py
from registries import callbacks_registry
@callbacks_registry.register
def cat():
print("Meow")
# dosomething.py
from registries import callbacks_registry
APPS = (
'app1',
'app2',
)
# Trigger autodiscovering process
callbacks_registry.autodiscover(APPS)
for callback in callbacks_registry.values():
callback()
# Wouf
# Meow
API
===
``Registry`` inherits from python built-in `collections.OrderedDict`, which means you can use regular dict methods to access registered data::
callbacks_registry.get("dog")() # will print Wouf
assert callbacks_registry.get("chicken", None) is None
Registry.register()
*******************
You can use this function as a decorator for registering functions and classes::
from persisting_theory import Registry
class AwesomeRegistry(Registry):
pass
r = AwesomeRegistry()
# register a class
@r.register
class AwesomeClass:
pass
# register a function
@r.register
def awesome_function():
pass
# By default, the key in the registry for a given value is obtained from the function or class name, if possible
assert r.get("AwesomeClass") == AwesomeClass
assert r.get("awesome_function") == awesome_function
# You can override this behaviour:
@r.register(name="Chuck")
class AwesomeClass:
pass
@r.register(name="Norris")
def awesome_function():
pass
assert r.get("Chuck") == AwesomeClass
assert r.get("Norris") == awesome_function
# You can also use the register method as is
awesome_var = "Chuck Norris"
r.register(awesome_var, name="Who am I ?")
assert r.get("Who am I ?") == awesome_var
# I f you are not registering a function or a class, you MUST provide a name argument
Registry.validate()
*******************
By default, a registry will accept any registered value. Sometimes, it's not what you want, so you can restrict what kind of data your registry accepts::
from persisting_theory import Registry
class StartsWithAwesomeRegistry(Registry):
def validate(self, data):
if isinstance(data, str):
return data.startswith("awesome")
return False
r = StartsWithAwesomeRegistry()
# will pass registration
r.register("awesome day", name="awesome_day")
# will fail and raise ValueError
r.register("not so awesome day", name="not_so_awesome_day")
Registry.prepare_data()
***********************
If you want to manipulate your data before registering it, override this method. In this example, we prefix every registered string with 'hello'::
from persisting_theory import Registry
class HelloRegistry(Registry):
def prepare_data(self, data):
return 'hello ' + data
r = HelloRegistry()
class Greeting:
def __init__(self, first_name):
self.first_name = first_name
r.register(Greeting('World'), name="world")
r.register(Greeting('Eliot'), name="eliot")
assert r.register.get('world') == "hello World"
assert r.register.get('eliot') == "hello Eliot"
Registry.prepare_name()
***********************
In a similar way, you can manipulate the name of registered data. This can help if you want to avoid repetitions. Let's improve our previous example::
from persisting_theory import Registry
class HelloRegistry(Registry):
def prepare_data(self, data):
return 'hello ' + data
def prepare_name(self, data, name=None):
return self.data.first_name.lower()
r = HelloRegistry()
class Greeting:
def __init__(self, first_name):
self.first_name = first_name
r.register(Greeting('World'))
r.register(Greeting('Eliot'))
assert r.register.get('world') == "hello World"
assert r.register.get('eliot') == "hello Eliot"
Going meta
**********
If you have multiple registries, or want to allow your apps to declare their own registries, this is for you::
# registries.py
from persisting_theory import meta_registry, Registry
class RegistryA(Registry):
look_into = "a"
class RegistryB(Registry):
look_into = "b"
registry_a = RegistryA()
meta_registry.register(registry_a, name="registry_a")
registry_b = RegistryB()
meta_registry.register(registry_b, name="registry_b")
# dosomethingelse.py
from persisting_theory import meta_registry
# will import registries declared in `registries` packages, and trigger autodiscover() on each of them
meta_registry.autodiscover(apps=("app1", "app2"))
What the hell is that name ?
============================
It's an anagram for "python registries".
Contribute
==========
Contributions, bug reports, and "thank you" are welcomed. Feel free to contact me at <contact@eliotberriot.com>.
License
=======
The project is licensed under BSD licence.
\ No newline at end of file
from registries import callbacks_registry
@callbacks_registry.register
def dog():
print("Wouf")
\ No newline at end of file
from registries import callbacks_registry
@callbacks_registry.register
def cat():
print("Meow")
\ No newline at end of file
from registries import callbacks_registry
APPS = (
'app1',
'app2',
)
# Trigger autodiscovering process
callbacks_registry.autodiscover(APPS)
for callback in callbacks_registry.values():
callback()
# Wouf
# Meow
\ No newline at end of file
import os, sys
sys.path.append(os.path.dirname(os.path.dirname(__file__)))
from persisting_theory import Registry
class CallbacksRegistry(Registry):
"""
Allow your apps to register callbacks
"""
# the package where the registry will try to find callbacks in each app
look_into = "callbacks_registry"
callbacks_registry = CallbacksRegistry()
APPS = (
'app1',
'app2',
)
# Trigger autodiscovering process
callbacks_registry.autodiscover(APPS)
\ No newline at end of file
Metadata-Version: 1.1
Name: persisting-theory
Version: 0.2.1
Summary: Registries that can autodiscover values accross your project apps
Home-page: http://code.eliotberriot.com/eliotberriot/persisting-theory
Author: Eliot Berriot
Author-email: contact@eliotberriot.com
License: BSD
Description: Introduction
============
Persisting-theory is a small python utility designed to automate data discovering and access inside a list of packages. Use case: you are building an application that will have pluggable components. You want to allow these components to register data so it can be accessed by any other component of your app.
If you ever used Django framework, you may remember this::
from django.contrib import admin
admin.autodiscover()
Basically, persisting-theory will do the same, except that it let you declare what you want to autodiscover.
Okay, I'm bad at explaining things, and english is not my mother tongue. Let's build a simple example.
Quickstart
==========
Install
*******
Install the package from `PyPi <https://pypi.python.org/pypi/persisting-theory/>`_. via pip (or any other tool)::
pip install persisting-theory
Persisting-theory does not require any dependency but a python installation (it has been tested on python 2.7 and python 3.2).
Setup
*****
A basic setup::
# registries.py
from persiting_theory import Registry
class CallbacksRegistry(Registry):
"""
Allow your apps to register callbacks
"""
# the package where the registry will try to find callbacks in each app
look_into = "callbacks_registry"
callbacks_registry = CallbacksRegistry()
# app1/callbacks_registry.py
from registries import callbacks_registry
@callbacks_registry.register
def dog():
print("Wouf")
# app2/callbacks_registry.py
from registries import callbacks_registry
@callbacks_registry.register
def cat():
print("Meow")
# dosomething.py
from registries import callbacks_registry
APPS = (
'app1',
'app2',
)
# Trigger autodiscovering process
callbacks_registry.autodiscover(APPS)
for callback in callbacks_registry.values():
callback()
# Wouf
# Meow
API
===
``Registry`` inherits from python built-in `collections.OrderedDict`, which means you can use regular dict methods to access registered data::
callbacks_registry.get("dog")() # will print Wouf
assert callbacks_registry.get("chicken", None) is None
Registry.register()
*******************
You can use this function as a decorator for registering functions and classes::
from persisting_theory import Registry
class AwesomeRegistry(Registry):
pass
r = AwesomeRegistry()
# register a class
@r.register
class AwesomeClass:
pass
# register a function
@r.register
def awesome_function():
pass
# By default, the key in the registry for a given value is obtained from the function or class name, if possible
assert r.get("AwesomeClass") == AwesomeClass
assert r.get("awesome_function") == awesome_function
# You can override this behaviour:
@r.register(name="Chuck")
class AwesomeClass:
pass
@r.register(name="Norris")
def awesome_function():
pass
assert r.get("Chuck") == AwesomeClass
assert r.get("Norris") == awesome_function
# You can also use the register method as is
awesome_var = "Chuck Norris"
r.register(awesome_var, name="Who am I ?")
assert r.get("Who am I ?") == awesome_var
# I f you are not registering a function or a class, you MUST provide a name argument
Registry.validate()
*******************
By default, a registry will accept any registered value. Sometimes, it's not what you want, so you can restrict what kind of data your registry accepts::
from persisting_theory import Registry
class StartsWithAwesomeRegistry(Registry):
def validate(self, data):
if isinstance(data, str):
return data.startswith("awesome")
return False
r = StartsWithAwesomeRegistry()
# will pass registration
r.register("awesome day", name="awesome_day")
# will fail and raise ValueError
r.register("not so awesome day", name="not_so_awesome_day")
Registry.prepare_data()
***********************
If you want to manipulate your data before registering it, override this method. In this example, we prefix every registered string with 'hello'::
from persisting_theory import Registry
class HelloRegistry(Registry):
def prepare_data(self, data):
return 'hello ' + data
r = HelloRegistry()
class Greeting:
def __init__(self, first_name):
self.first_name = first_name
r.register(Greeting('World'), name="world")
r.register(Greeting('Eliot'), name="eliot")
assert r.register.get('world') == "hello World"
assert r.register.get('eliot') == "hello Eliot"
Registry.prepare_name()
***********************
In a similar way, you can manipulate the name of registered data. This can help if you want to avoid repetitions. Let's improve our previous example::
from persisting_theory import Registry
class HelloRegistry(Registry):
def prepare_data(self, data):
return 'hello ' + data
def prepare_name(self, data, name=None):
return self.data.first_name.lower()
r = HelloRegistry()
class Greeting:
def __init__(self, first_name):
self.first_name = first_name
r.register(Greeting('World'))
r.register(Greeting('Eliot'))
assert r.register.get('world') == "hello World"
assert r.register.get('eliot') == "hello Eliot"
Going meta
**********
If you have multiple registries, or want to allow your apps to declare their own registries, this is for you::
# registries.py
from persisting_theory import meta_registry, Registry
class RegistryA(Registry):
look_into = "a"
class RegistryB(Registry):
look_into = "b"
registry_a = RegistryA()
meta_registry.register(registry_a, name="registry_a")
registry_b = RegistryB()
meta_registry.register(registry_b, name="registry_b")
# dosomethingelse.py
from persisting_theory import meta_registry
# will import registries declared in `registries` packages, and trigger autodiscover() on each of them
meta_registry.autodiscover(apps=("app1", "app2"))
What the hell is that name ?
============================
It's an anagram for "python registries".
Contribute
==========
Contributions, bug reports, and "thank you" are welcomed. Feel free to contact me at <contact@eliotberriot.com>.
License
=======
The project is licensed under BSD licence.
Platform: UNKNOWN
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: BSD License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3.4
CHANGES
COPYING
MANIFEST.in
README.rst
setup.py
example/__init__.py
example/dosomething.py
example/registries.py
example/app1/__init__.py
example/app1/callbacks_registry.py
example/app2/__init__.py
example/app2/callbacks_registry.py
persisting_theory/__init__.py
persisting_theory/registries.py
persisting_theory.egg-info/PKG-INFO
persisting_theory.egg-info/SOURCES.txt
persisting_theory.egg-info/dependency_links.txt
persisting_theory.egg-info/not-zip-safe
persisting_theory.egg-info/top_level.txt
tests/__init__.py
tests/test_registries.py
tests/tests.py
tests/app1/__init__.py
tests/app1/awesome_people.py
tests/app1/vegetables.py
tests/app2/__init__.py
tests/app2/awesome_people.py
tests/app2/vegetables.py
tests/buggy_app/__init__.py
tests/buggy_app/awesome_people.py
\ No newline at end of file
tests
example
persisting_theory
from .registries import Registry, meta_registry
__version__ = "0.2.1"
\ No newline at end of file
from collections import OrderedDict
import inspect
try:
# use Python3 reload
from imp import reload
except:
# we are on Python2
pass
class Registry(OrderedDict):
def register_decorator_factory(self, **kwargs):
"""
Return an actual decorator for registering objects into registry
"""
name = kwargs.get('name')
def decorator(decorated):
self.register_func(data=decorated, name=name)
return decorated
return decorator
def register(self, data=None, name=None, **kwargs):
"""
Use this method as a decorator on class/function you want to register:
@registry.register(name="test")
class Test:
pass
:param:data: Something to register in the registry
:param:name: The unique name that will identify registered data.
If None, by default, registry will try to deduce name from class name (if object is a class or an object).
You can change this behaviour by overriding :py::method:`prepare_name`
"""
if data is None:
return self.register_decorator_factory(data=data, name=name, **kwargs)
else:
self.register_func(data=data, name=name, **kwargs)
return data
def get_object_name(self, data):
"""
Return a name from an element (object, class, function...)
"""
if callable(data):
return data.__name__
elif inspect.isclass(data):
return data.__class__.__name__
else:
raise ValueError("Cannot deduce name from given object ({0}). Please user registry.register() with a 'name' argument.".format(data))
def validate(self, data):
"""
Called before registering a new value into the registry
Override this method if you want to restrict what type of data cna be registered
"""
return True
def prepare_name(self, data, name=None):
if name is None:
return self.get_object_name(data)
return name
def register_func(self, data, name=None, **kwargs):
"""
Register abritrary data into the registry
"""
if self.validate(data):
o = self.prepare_data(data)
n = self.prepare_name(data, name)
self[n] = o
self.post_register(data=0, name=n)
else:
raise ValueError("{0} (type: {0.__class__}) is not a valid value for {1} registry".format(data, self.__class__))
def post_register(self, data, name):
"""
Will be triggered each time a new element is successfully registered.
Feel free to override this method
"""
pass
def prepare_data(self, data):
"""
Override this methode if you want to manipulate data before registering it
You MUST return a value to register
"""
return data
def autodiscover(self, apps, force_reload=False):
"""
Iterate throught every installed apps, trying to import `look_into` package
:param apps: an iterable of string, refering to python modules the registry will try to import via autodiscover
"""
for app in apps:
app_package = __import__(app)
try:
package = '{0}.{1}'.format(app, self.look_into) # try to import self.package inside current app
#print(package)
module = __import__(package)
if force_reload:
reload(module)
except ImportError as exc:
# From django's syncdb
# This is slightly hackish. We want to ignore ImportErrors
# if the module itself is missing -- but we don't
# want to ignore the exception if the module exists
# but raises an ImportError for some reason. The only way we
# can do this is to check the text of the exception. Note that
# we're a bit broad in how we check the text, because different
# Python implementations may not use the same text.
# CPython uses the text "No module named"
# PyPy uses "No module named myproject.myapp"
msg = exc.args[0]
if not msg.startswith('No module named') or self.look_into not in msg:
raise
class MetaRegistry(Registry):
"""
Keep a reference to all registries
"""
look_into = "registries"
def autodiscover(self, apps, cascade=True, **kwargs):
"""
:param cascade: If true, will trigger autodiscover on discovered registries
"""
super(MetaRegistry, self).autodiscover(apps, **kwargs)
if cascade:
self.autodiscover_registries(apps)
def autodiscover_registries(self, apps):
for key, registry in self.items():
registry.autodiscover(apps)
meta_registry = MetaRegistry()
\ No newline at end of file
[egg_info]
tag_date = 0
tag_build =
tag_svn_revision = 0
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment