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
[Positive review] dsage.setup() add_default_client broken #3314
Comments
Attachment: 3314_default_users.patch.gz |
Changed keywords from none to editor_gfurnish |
comment:5
DSage is completely broken in 3.0.2 and 3.0.3!!!!! Make me some patches so that I can actually run dsage. |
comment:6
DSage is not completely broken in Sage 3.0.2 with the patch applied and in 3.3.0.rc0. If you make claims like that you should back them up with details. Cheers, Michael |
comment:7
If you do not have an existing known good .sage directory with existing dsage materials from some previous version (unknown), dsage is completely broken. |
comment:8
Ok, the bug is the following after deleting the dsage directory in DOT_SAGE:
The DSage server log says:
Cheers, Michael |
comment:9
Michael, Gary, did you test this after applying the patch I posted? |
comment:13
Merged in Sage 3.0.3.final |
twisted changed it's conch interface and I forgot to toString the pubkey object in some instances.
Component: dsage
Keywords: editor_gfurnish
Issue created by migration from https://trac.sagemath.org/ticket/3314
The text was updated successfully, but these errors were encountered: