I can't imagine that anyone is using FastHashable_class, except for > CategorySingleton. Nevertheless, Travis insists that we should keep > FastHashable_class available in sage.categories.category_singleton, with > a deprecation warning. > > But how? Is there a standard way to deprecate an import location for a > class? > > Ideally, the attempt to cimport (not import!) FastHashable_class would > result in a compile time warning, pointing to the new location. But at > least, I would like that > from sage.categories.category_singleton import FastHashable_class > results in a deprecation warning, but does import a class (so that one > could inherit from it). > > I would really like to see the deprecation warning when it is > *imported*, but not when its first instance is created (which might be > doable with some ClasscallMetaclass magic). > > Is there a lazy_import with deprecation? >
See http://trac.sagemath.org/sage_trac/ticket/14275. I'm not sure that it's exactly what you're looking for, but I welcome suggestions. David -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
