* This implementation is *not* thread-safe, in and of itself. If you're
in a multi-threaded environment, wrap object instantiation in a lock.
- * Be careful with call signatures. This metaclas
+ * Be careful with call signatures. This metaclas
caches on call signature, which can vary if keyword args
are used. E.g. ``def func(a, b=2)`` could be called ``func(1)``, ``func(1,2)``,
``func(a=1)``, ``func(1, b=2)``, or ``func(a=2, b=2)``--and all resolve to the
This may degrade performance, and can also create
errors, if you're counting on ``mementos`` to create just one object.
- So don't do that. Use
the same calling style, and it won't be a problem.
+ So don't do that. Use calling style, and it won't be a problem.
In most cases, this isn't an issue, because objects tend to be
instanitated with a limited number of parameters, and you can take care
description='Memoizing metaclass. Drop-dead simple way to create cached objects',