Robert Scott

I've been experimenting with simply making `NestedMutable`'s choice of `dict` and `list` implementations exposed and overridable a la: ``` class NestedMutable(Mutable): """SQLAlchemy `mutable` extension with nested change tracking.""" MUTABLE_DICT_TYPE =...

The last to get hit is actually the `.changed()` of `Mutable` itself, and if you needed to intercept the call _after_ `TrackedObject.changed(...)` but _before_ `Mutable.changed()` it's (probably?) impossible to do...

_Including_ methods is still worthwhile especially when the methods have long and verbose call signatures.

We started seeing this in the cnvkit NixOS package when we moved from pysam 0.17.0 to 0.18.0. Full build log including failure: https://hydra.nixos.org/log/4xh8l9vv6gm4lgjglb033aaa414bn8sb-python3.10-CNVkit-0.9.7.drv Same error if we try with 0.9.9

This error was only added in 0.18.0 https://github.com/pysam-developers/pysam/commit/6a170cfaa0ab562e2ae597a383f5c5134818d23e#diff-93a78e45fea134d909b59bf25d4e6394bfdbbc27f95bd28a381a856ceb03195f

CVE-2020-10810: https://github.com/HDFGroup/hdf5/commit/267ff9065ba9f42fec05cdcae0caa90536a04392 ?

CVE-2020-10811: Included in https://github.com/HDFGroup/hdf5/commit/dafc7285bb1df4a6529a64c215c5de4017016d24 ? Claimed to be the same issue as CVE-2018-14033

Is there any progress on this? flask-sqlalchemy >=3 support will allow us (NixOS) to fix our flask-appbuilder package.

On darwin x86_64, I see this failure too, though as of 0.22.0 we're only seeing it for `test_ellipse_parameter_stability`.

This is what we're currently using, so I may as well un-draft it.