I think the error message is clear enough, you shouldn't be resolving
lazy imports on Sage startup. Usually, lazy imports are used to limit
the amount of imports done at Sage startup. So if a lazy import is used
during Sage startup, that's usually a bug.
Now the underlying problem is that you use is_package_installed() in
code which is executed on startup. I suggest you try to refactor your
code to avoid the use of is_package_installed (for example, use
try:/except ImportError: instead).
On 2014-12-18 12:44, Vincent Knight wrote:
Resolving lazy import is_package_installed during startup
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
