Re: [sage-devel] Re: Do we have a "deprecated_module_alias" ?

2014-12-01 Thread Travis Scrimshaw
IIRC, the deprecation message is printed when the module is actually imported. To do what you're suggesting, one could add a call to deprecation() at the module level (which is executed when the import is called). Best, Travis On Monday, December 1, 2014 8:22:34 AM UTC-8, vdelecroix wrote: >

Re: [sage-devel] Re: Do we have a "deprecated_module_alias" ?

2014-12-01 Thread Vincent Delecroix
Hi Travis, I am not sure that it is what Nathann wanted. The all.py in crystals deprecate objects from the global namespace but not modules. In particular, you do not have something which behave like {{{ sage: import old_module Warning: Deprecation !! See trac ticket #42 for more info! sage: old_m

[sage-devel] Re: Do we have a "deprecated_module_alias" ?

2014-12-01 Thread Travis Scrimshaw
There's a deprecation keyword one can use with lazy_import. See combinat/crystals/all.py for examples. Best, Travis On Monday, December 1, 2014 5:54:08 AM UTC-8, Nathann Cohen wrote: > > Hello everybody ! > > I just met two situations in which we need to rename a module: 1) not > in the right