Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

a bug in startup_modules plugin? #71

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

Comments

Projects
None yet
3 participants
@dimpase
Copy link
Member

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

This comment has been minimized.

Copy link
Contributor

commented Sep 26, 2015

@fchapoton

This comment has been minimized.

Copy link
Collaborator

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

This comment has been minimized.

Copy link
Collaborator

commented May 22, 2016

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

@fchapoton fchapoton closed this May 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.