| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This had me reread the code twice to see if I missed why the import was
present.
|
| |
|
|
|
|
| |
versionadded
|
| |
|
|
|
|
|
|
| |
We should probably reword this entirely as, IMHO, this should be in the
changelog and not in the doc proper (which should only describe the
current state of affairs).
|
|
|
|
|
| |
if the given target/event/fn is set up to listen.
- repair mutable package which is doing some conditional event listening
|
|
|
|
| |
- simplify
|
| |
|
|
|
|
| |
before checking if it is a subclass of `MutableComposite`
|
|
|
|
|
| |
when ``clear()`` was called.
[ticket:2730]
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
:meth:`.MutableBase.coerce` method to be used, even though
the code seemed to indicate this intent, so this now works
and a brief example is added. As a side-effect,
the mechanics of this event handler have been changed so that
new :class:`.MutableComposite` types no longer add per-type
global event handlers. Also in 0.7.10
[ticket:2624]
|
| |
|
| |
|
|
|
|
| |
- this was a mistake in mutable
|
| |
|
| |
|
|
|
|
| |
such as ``.. versionadded::``, ``.. versionchanged::`` and ``.. deprecated::``.
|
| |
|
| |
|
|
|
|
| |
no longer compatible with docutils 0.8
|
|
|
|
|
|
|
| |
if None or a non-corresponding type were set,
an error would be raised. None is now accepted
which assigns None to all attributes,
illegal values raise ValueError.
|
|
|
|
|
|
| |
if the same type were used twice in one
mapping, the attributes beyond the first
would not get instrumented.
|
|
|
|
|
|
| |
events to subclasses correctly; don't
create multiple event listeners for
subclasses either. [ticket:2180]
|
|
|
|
|
|
| |
`None` was not appropriately handled, replacement
events were not appropriately handled.
[ticket:2143]
|
|
|
|
|
|
| |
abc from the ext.mutable docs as it was being used
incorrectly and makes the example more difficult
to understand in any case. [ticket:2152]
|
|
|
|
|
| |
correct type-association methods.
[ticket:2118]
|
| |
|
|
|
|
|
|
|
| |
- add pickle/unpickle events to ORM events. these are needed
for the mutable extension.
- finish mutable extension documentation, consolidate examples,
add full descriptions
|
| |
|
|
|
|
|
| |
a consistent tag
- AUTHORS file
|
|
|
|
|
|
| |
- add list of attribute names to refresh()
- ensure refresh() only called when attributes actually refreshed
- tests. [ticket:2011]
|
| |
|
|
- streamline interfaces, get Mutable/MutableComposite to be as minimal
in usage as possible
- docs for mutable, warnings regrarding mapper events being global
- move MutableType/mutable=True outwards, move orm tests to its
own module, note in all documentation
- still need more events/tests for correct pickling support of
composites, mutables. in the case of composites its needed
even without mutation. see [ticket:2009]
|