[10:21]<simono> if i understand ng's import() correctly its broken [10:21]<simono> import('helma/term', 'term') should be the same as import('helma/term') right? [10:21]<simono> the latter doesnt create 'term' in the caller's scope [11:18]<simono> hannesw_: ^^ am i using import wrong? [11:19]<hannesw_> import('helma/term') creates helma.term [11:19]<hannesw_> but that may be wrong [11:19]<hannesw_> should it create "term"? [11:19]<hannesw_> I'm open to changes [11:22]<simono> okay helma.term, i misunderstood [11:23]<zumbrunn> I happen to like the fact that it creates helma.term [11:24]<zumbrunn> it's more in line with my preference for the modules.helma.term way of accessing modules [11:24]<zumbrunn> and I am currently using it in that spirit [11:24]<zumbrunn> but I understand that one could see it as wrong/unexpected behavior [11:27]<simono> that is reasonable. but i don't like that the imported moduleName is tied to the "path" to that module [11:29]<simono> at least one advantage of not tying to path, which is often used in python :), is that you can make transitions easier [11:31]<simono> import('helma.date') and use date.format in your code [11:31]<simono> then commonjs standardizes it and we can just change the import to import('commonjs.date') and all is good [11:46]<zumbrunn> I have no objection to changing the way import works, except that I will miss the old behavior ;-) [11:58]<simono> only reporting pros of different behaviour.. ;) i'm always biased pro-python-way which sometimes bites me [16:41]<simono> made a rough interactive help for NG http://github.com/oberhamsi/jsinterhelp [16:41]<simono> (seems the github website is not up2date... oh well) [16:46]<simono> f