Skip to content
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.

a bug in startup_modules plugin? #71

Closed
dimpase opened this issue Aug 28, 2015 · 3 comments
Closed

a bug in startup_modules plugin? #71

dimpase opened this issue Aug 28, 2015 · 3 comments

Comments

@dimpase
Copy link
Member

dimpase commented Aug 28, 2015

On #18997 (http://patchbot.sagemath.org/ticket/18997/) I saw PluginFailed - on startup_modules, which appears to be caused by innocent things like

   from itertools import combinations

The patchbots seem to think that "sage.combinat.designs.itertools" is a valid module name, see e.g.
http://patchbot.sagemath.org/ticket/18997/plugin/plugins.startup_modules/2015-08-26%2006:41:06%20+0000/

@videlec
Copy link
Contributor

videlec commented Sep 26, 2015

@fchapoton
Copy link
Collaborator

fchapoton commented Apr 27, 2016

This is triggered by a call to

print '\n'.join(sorted(sys.modules.keys()))

which gives many wrong module names, such as sage.misc.builtin or sage.misc.future

@fchapoton
Copy link
Collaborator

This is solved in patchbot 2.5.7, which has a better handling of the startup module.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants