Increased test coverage for serialization

[lumip]

Closes #294

I looked into coveralls to see which lines/branches are not yet covered by tests.
In particular the case in Serializable.init() where a pulse might get registered only after the gc is invoked was not covered. I tried to do this (delete a registered pulse with del while explicitely disabling the automatic gc) but couldn't cause the desired behavior. Are we sure that the invocation of the gc is necessary at that point?
Also, there's the issue of the AnonymousSerializable. It is currently not neatly integrated into the Serializable class tree and should really be (or be an abstract class defining abstract methods).

[coveralls]

Coverage increased (+0.07%) to 94.147% when pulling 0d1f9df on issues/250_one_more_test into 42b888d on issues/250_serialization.

[terrorfisch]

Are we sure that the invocation of the gc is necessary at that point?

I think it can be removed as the default_storage_backend isn't a WeakValueDictionary by default anymore.

Also, there's the issue of the AnonymousSerializable. It is currently not neatly integrated into the Serializable class tree and should really be (or be an abstract class defining abstract methods).

An ABCMeta metaclass makes calling isinstance much more costly(~10) and we call isinstance with Expression as type quite a lot. We could drop this and just check if the object we want to serialize has a get_serialization_data attribute here: https://github.com/qutech/qc-toolkit/blob/9548742bb565ce50171eacfd8e47eff02df6b0d8/qctoolkit/serialization.py#L861

[lumip]

I think it can be removed as the default_storage_backend isn't a WeakValueDictionary by default anymore.

hm.. but in principle it's still possible to set the default_storage_backend as a WeakValueDictionary so if the gc invocation is necessary in that case we shouldn't just remove that (although the tests I did worked fine without the gc even for WeakValueDictionary but that might be luck?)... However, the weakref documentation states that

if the referent is no longer alive, calling the reference object will cause None to be returned

so I guess, instead of invoking the garbace collector, we can just check whether the object currently stored in the registry (if any) is None ..?

An ABCMeta metaclass makes calling isinstance much more costly(~10) and we call isinstance with Expression as type quite a lot. We could drop this and just check if the object we want to serialize has a get_serialization_data attribute here:

-.-
well.. in that case I guess it's best to leave it as it is right now (and maybe try to find a nicer solution for the Expressions in the long run..?)

[terrorfisch]

hm.. but in principle it's still possible to set the default_storage_backend as a WeakValueDictionary so if the gc invocation is necessary in that case we shouldn't just remove that (although the tests I did worked fine without the gc even for WeakValueDictionary but that might be luck?)... However, the weakref documentation states that

IMHO, if the user sets it as an WeakValueDict, he is responsible for cleaning up. If desired we could provide tools for this.

[terrorfisch]

Merge if you think this is ok.