At 11:37 AM 4/21/2006 -0500, Ian Bicking wrote: >Phillip J. Eby wrote: >>The second is that PEP 302 only covers "location" importers, not "format" >>importers. That is, if you want to do something like make Kid or Cheetah >>templates importable, you have to replace things with new >>machinery. This is a more important problem to solve, IMO, than coming >>up with yet another set of semantics for the things that *are* covered by >>PEP 302. > >I think the specific examples (Kid and Cheetah) are places where import >machinery is used when it shouldn't be. Or at least, when it would be >better to use more path-based machinery.
Actually, *my* use cases for this mechanism would run more to running other languages in the Python VM. For example, Logix or my SCALE experiments, or that project, I think it's called "classpath", that lets you import Java classes in Python. The main reason I mentioned the template use cases is because they currently exist and have users. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
