Hmm, I see the issue. Could we solve it by dispatching explicitly after the linking stage?

The reason I did this, was because when a `ConfigParserProperty` is created with a `name`, we register this property with the `ConfigParser` class, so that when a `ConfigParser` instance with this `name` is created , the `ConfigParserProperty` is notified by the `ConfigParser` class so that it can connect itself to this parser instance.

The problem arose, such that if the parser already existed at the time of property creation, then from `link_deps` when I register the property with `ConfigParser`, since the parser already exists, `ConfigParser` immediately calls the property. However because setattr happened _after_ `link_deps`, an error arose because the class didn't know yet about the property.

This really is an issue with properties not having a stage which gets called after the properties get fully created. If there was such a function in Property, e.g. `on_ready`, then I could register with `ConfigParser` from there and everything is fine. As it is, `link_deps` is the last appropriate function called, so I'm forced to register from there.