[Python-Dev] Questions about '@' in pep 318

[Edward K. Ream]

> That requires all annotations to be in the __future__ module. This is not
acceptable, as there is a desire to provide user-defined annotations as
well.

Oh dear.  Does this mean that @x is a potential annotation for any
identifier x?  This would be very bad for Leo.

I was using __future__ by way of explanation.  I do hope namespaces could
somehow denote annotations.  My off-the-cuff suggestion was for
pseudo-modules, so maybe the normal module rules could be sidestepped?

Edward
--------------------------------------------------------------------
Edward K. Ream   email:  edreamleo at charter.net
Leo: Literate Editor with Outlines
Leo: http://webpages.charter.net/edreamleo/front.html
--------------------------------------------------------------------