On Feb 21, 11:24 am, kcrisman <kcris...@gmail.com> wrote: > Some of the > issue might be that the developer guide isn't explicit enough about > how to import things like this?
+1 Like KDC, I never know whether to import at the top of a module, inside a method, inside a loop,..., even though I know the various possibilities have an effect on startup and run times. And then do I import from sage.all, or sage.rings, or do I import the whole module, do I use "from blah import *" or "from blah import stuff". And I have no idea how to do a lazy import. I do know the trick used to avoid importing SciPy over and over again. But I'm not looking for answers right here. The point is, I'm sure I've made some bad choices and reviewers have not known better either. Some education would help, I think. If somebody who knows what they are talking about could vastly improve: http://www.sagemath.org/doc/developer/coding_in_python.html#importing then coders and reviewers would have a place to go (and point to) and maybe the situation will not get worse, and when folks have their heads inside something they could improve existing code. cc me and I'll review it. Rob -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
