Dirk,
If the memory patch uses __slots, then won't that likely break some user
logic? If so then we should push out 2.3.1 without it with a notice in the
release notes indicating what such change may break?
Also looks like we have more than a handful of tests broken.
So my suggestion would be to
Bill,
On 17.12.2013 22:06, Bill Deegan wrote:
Dirk,
If the memory patch uses __slots, then won't that likely break some
user logic? If so then we should push out 2.3.1 without it with a
notice in the release notes indicating what such change may break?
this patch doesn't use slots at