lazy_imported stuff in sage.coding is in many cases immediately dereferenced

Issue #131 resolved
Johan Rosenkilde created an issue

If a module has been lazily imported, it shouldn't show up when browsing the parent module. However, on a freshly opened sage, doing sage.coding.<tab> gives

sage.coding.all                    sage.coding.code_bounds            sage.coding.delsarte_bounds        sage.coding.linear_code
sage.coding.channel_constructions  sage.coding.code_constructions     sage.coding.guava                  sage.coding.sd_codes

Several of these are lazily imported but show up anyway (e.g. delsarte_bounds), and some of them should be lazily imported but aren't. In the case of delsarte_bounds, it might be due to code_bounds referring to it, and `code_bounds is not lazily imported (but should be).

Comments (2)

  1. Log in to comment