Hello, As far as I can see (in sage.misc.superseded, no). Might be useful to have one. But where would you define it ? in the new module ? in the all.py of the parent module ? as the unique line in the old file ? Note that it might be tricky to declare if you do not want it in the global namespace.
Best Vincent 2014-12-01 14:54 UTC+01:00, Nathann Cohen <nathann.co...@gmail.com>: > Hello everybody ! > > I just met two situations in which we need to rename a module: 1) not > in the right folder; or 2) not the right name. > > Do we currently have a "deprecated_module_alias" implemented in a way > that I did not notice ? We would need to have a "fake" module > pointing toward the real one, which raises an exception the first time > it is imported. > > Thanks ! > > Nathann > > -- > 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. > -- 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.
