On Mon, Aug 9, 2010 at 11:46 AM, Dino Viehland <di...@microsoft.com> wrote: > My biggest concern w/ using import semantics for this is Brett's goal > (which I am +100 on) to move to a Python implementation of import. > Once that happens it'll be either very difficult or impossible to > make this syntax work. Even import clr will need to change to be > something we recognize at compile time like from __future__. So I'm > inclined not to do that - plus it may be boarding too close on > embracing and extending :)
Oh right, I forgot about that project - presumably all the Pythons would share their import code? That'll go nicely with a split-out standard library. In that case, making the clr module the entry point for all of IronPython's magic is the best idea. For 3.2, maybe it should change to __clr__ so that it's clear that it's magic - things are going to break anyway, and it would be an easy 2to3 fixer. Or see if Guido will let you borrow the time machine :). - Jeff _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
