key_predicatefunction is gone. You can now use
class_predicatefunction is gone. You can now use
NOT_FOUNDobject are gone.
PredicateRegistryis not longer part of the API. Internally, the classes
SingleValueRegistryhave all been merged into
PredicateRegistry, which should now considered an implementation detail.
The second argument for
match_keyis now optional; if you don’t supply it
match_keywill generate a predicate function that extracts that name by default.
The documentation now includes a section describing the internals of Reg.
Upload universal wheels to pypi during release.
Reg has undergone another API breaking change. The goals of this change were:
- Make everything explicit.
- A simpler implementation structure – dispatch functions maintain their own registries, which allows for less interacting objects.
- Make the advanced context-dependent dispatch more Pythonic by using classes with special dispatch methods.
reg.Registryis gone. Instead you register directly on the dispatch function:
@reg.dispatch('a') def foo(a): ... def foo_implementation(a): ... foo.register(foo_implementation, a=Document)
Caching is now per dispatch function, not globally per lookup. You can pass a
get_key_lookupfunction that wraps
reg.PredicateRegistryinstance inside a
reg.DictCachingKeyLookupcache. You can also use a
reg.LruCachingKeyLookupif you expect a dispatch to be called with a large amount of possible predicate combinations, to preserve memory.
The whole concept of a “lookup” is gone:
reg.implicitis gone: everything is explicit. There is no more implicit lookup.
reg.Lookupitself is gone – its now implemented directly in the dispatch object, but was already how you accessed it.
- The special
lookupargument to pass through the current
Lookupis gone. If you need context-dependent dispatch, you use dispatch methods.
- If you need context dependent dispatch, where the functions
being dispatched to depend on application context (such as
Morepath’s application mounting), you use
reg.dispatch_methodto create a dispatch method. A dispatch method maintains an entirely separate dispatch registry for each subclass. You use
reg.methodifyto register a dispatch function that takes an optional context first argument.
If you do not use the context-dependent dispatch feature, then to upgrade your code:
reg.set_implicitfrom your code, setup of
Lookupand the like.
If you use an explicit
lookupargument you can just remove them.
You also need to change your registration code: no more
Change your registrations to be on the dispatch objects itself using
To enable caching you need to set up
get_key_lookupon the dispatch functions. You can create a partially applied version of
dispatchto make this less verbose:
import reg from functools import partial def get_caching_key_lookup(r): return reg.CachingKeyLookup(r, 5000, 5000, 5000) dispatch = partial(reg.dispatch, get_key_lookup=get_caching_key_lookup)
dispatch_external_predicatesis gone. Just use
dispatchdirectly. You can add predicates to an existing Dispatch object using the
If you do use the context-dependent dispatch feature, then you also need to:
- identify the context class in your application (or create one).
- move the dispatch functions to this class, marking them with
- Registration is now using
<context_class>.<method>.register. Functions you register this way behave as methods to
context_class, so get an instance of this class as the first argument.
- You can also use
reg.methodifyto register implementation functions that do not take the context as the first argument – this is useful when upgrading existing code.
- Call your context-dependent methods as methods on the context instance. This way you can indicate what context you are calling your dispatch methods in, instead of using the lookup` argument.
In some cases you want a context-dependent method that actually does not dispatch on any of its arguments. To support this use case you can simply set function (that takes an app argument) as a the method on the context class directly:
Context.my_method = some_function
If you want to set up a function that doesn’t take a reference to a
Contextinstance as its first argument, you can use
reg.methodifyto turn it into a method that ignores its first argument:
Context.my_method = reg.methodify(some_function)
If you want to register a function that might or might not have a reference to a
Contextinstance as its first argument, called, e.g.,
app, you can use the following:
Context.my_method = reg.methodify(some_function, selfname='app')
Removed the helper function
mapplyfrom the API.
Removed the exception class
KeyExtractorErrorfrom the API. When passing the wrong number of arguments to a dispatch function, or when using the wrong argument names, you will now get a TypeError, in conformity with standard Python behaviour.
KeyExtractorclass from the API. Callables used in predicate construction now expect the same arguments as the dispatch function.
Predicateand its descendant.
match_argnamepredicate. You can now use
match_instancewith no callable instead.
The second argument for
match_classis now optional; if you don’t supply it
match_classwill generate a predicate function that extracts that name by default.
The second argument for
match_instanceis now optional; if you don’t supply it
match_instancewill generate a predicate function that extracts that name by default.
Include doctests in Tox and Travis.
We now use virtualenv and pip instead of buildout to set up the development environment. The development documentation has been updated accordingly.
As we reached 100% code coverage for pytest, coveralls integration was replaced by the
coverage reportin the tox coverage test.
- Minor fixes to documentation.
- Add tox test environments for Python 3.4 and 3.5, PyPy 3 and PEP 8.
- Make Python 3.5 the default Python environment.
- Changed location
NoImplicitLookupErrorwas imported from in
- Reg was a bit too strict; when you had multiple (but not single) predicates, Reg would raise KeyError when you put in an unknown key. Now they’re just being silently ignored, as they don’t do any harm.
- Eliminated a check in
ArgExtractorthat could never take place.
- Bring test coverage back up to 100%.
- Add converage configuration to ignore test files in coverage reporting.
- A bugfix in the behavior of the fallback logic. In situations with multiple predicates of which one is a class predicate it was possible for a fallback not to be found even though a fallback was available.
Total rewrite of Reg! This includes a range of changes that can break code. The primary motivations for this rewrite:
- unify predicate system with class-based lookup system.
- extract dispatch information from specific arguments instead of all arguments.
Some specific changes:
@reg.dispatch()decorator. This decorator can be configured with predicates that extract information from the arguments. Rewrite this:
@reg.generic def foo(obj): pass
@reg.dispatch('obj') def foo(obj): pass
@reg.generic def bar(a, b): pass
@reg.dispatch('a', 'b') def bar(a, b): pass
This is to get dispatch on the classes of these instance arguments. If you want to match on the class of an attribute of an argument (for instance) you can use
match_instancewith a function:
@reg.dispatch(match_instance('a', lambda a: a.attr))
The first argument to
match_instanceis the name of the predicate by which you refer to it in
You can also use
match_classto have direct dispatch on classes (useful for replicating classmethods), and
match_keyto have dispatch on the (immutable) value of the argument (useful for a view predicate system). Like for
match_instance, you supply functions to these match functions that extract the exact information to dispatch on from the argument.
register_functionAPI replaces the
registerAPI to register a function. Replace this:
r.register(foo, (SomeClass,), dispatched_to)
r.register_function(foo, dispatched_to, obj=SomeClass)
You now use keyword parameters to indicate exactly those arguments specified by
reg.dispatch()are actually predicate arguments. You don’t need to worry about the order of predicates anymore when you register a function for it.
classgenericfunctionality is part of the predicate system now; you can use
@reg.classgeneric def foo(cls): pass
@reg.dispatch(reg.match_class('cls', lambda cls: cls)) def foo(cls): pass
You can do this with any argument now, not just the first one.
pep443 support is gone. Reg is focused on its own dispatch system.
Compose functionality is gone – it turns out Morepath doesn’t use lookup composition to support App inheritance. The cached lookup functionality has moved into
registry.pyand now also supports caching of predicate-based lookups.
Dependency on the future module is gone in favor of a small amount of compatibility code.
- Added a
@reg.classgeneric. This is like
@reg.generic, but the first argument is treated as a class, not as an instance. This makes it possible to replace
@classmethodwith a generic function too.
- Fix documentation on running documentation tests. For some reason this did not work properly anymore without running sphinxpython explicitly.
- Optimization: improve performance of generic function calls by
lookup_mapplyinstead of general
mapply, as we only care about passing in the lookup argument when it’s defined, and any other arguments should work as before. Also added a
perf.pywhich is a simple generic function timing script.
- Python 2.6 compatibility. (Ivo van der Wijk)
- Class maps (and thus generic function lookup) now works with old style classes as well.
- Marked as production/stable now in
- Removed unused code from mapply.py.
- Typo fix in API docs.
reg.ANYpublic. Used for predicates that match any value.
- arginfo has been totally rewritten and is now part of the public API of reg.
- Experimental Python 3.3 support thanks to the future module.
- If a generic function implementation defines a
lookupargument that argument will be the lookup used to call it.
reg.mapply(). This allows you to call things with more keyword arguments than it accepts, ignoring those extra keyword args.
- A function that returns
Noneis not assumed to fail, so no fallback to the original generic function is triggered anymore.
- An optional
precalcfacility is made available on
Matcherto avoid some recalculation.
- Implement a specific
PredicateMatcherthat matches a value on predicate.
- Initial public release.