Support for postponed evaluation of annotations about middle HOT 3 OPEN

I think for middle it would be a relatively simple change, but it is a 3.7+ change. Just a thought.

It may be simple, yes, but I intend to support Python 3.6 yet for middle 0.3.x. I know that middle uses some metaclass magic and perhaps I could workaround that, but I feel this would not be possible since middle evaluates the classes during declaration - or I could lazily evaluate them as they are registered and replacing the defined classes in runtime. Hmmm, this does need some testing to see if it can be done with Python 3.6 and would not break evaluation ...

from middle.

I have not tried it... but does middle accept string annotations?

class Foo:
    bars: List["Bar"]

from middle.

I have not tried it... but does middle accept string annotations?

Nope, a str is a str (for now). I was thinking about:

class Foo:
    bars: List[middle.lazy("Bar")]

Instead of the lazy annotations, but this will fall into the same problem as I mentioned earlier: lazily evaluate the entire class only when all classes are available and reload them inside sys.modules ... A bit hacky, I don't know if it'll work properly but it'll be almost the same thing as the metaclass making this magic (I guess).

from middle.