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

py3: src/sage/numerical/backends/glpk_graph_backend #26020

Closed
jdemeyer opened this issue Aug 7, 2018 · 5 comments
Closed

py3: src/sage/numerical/backends/glpk_graph_backend #26020

jdemeyer opened this issue Aug 7, 2018 · 5 comments

Comments

@jdemeyer
Copy link

jdemeyer commented Aug 7, 2018

Subpatch of #24740

CC: @embray

Component: python3

Author: Erik Bray

Branch/Commit: 73e4365

Reviewer: Jeroen Demeyer

Issue created by migration from https://trac.sagemath.org/ticket/26020

@jdemeyer jdemeyer added this to the sage-8.4 milestone Aug 7, 2018
@jdemeyer
Copy link
Author

jdemeyer commented Aug 7, 2018

Branch: u/jdemeyer/ticket/26020

@jdemeyer
Copy link
Author

jdemeyer commented Aug 7, 2018

New commits:

73e4365py3: numerous string encode/decode fixes for sage.numerical.backends

@jdemeyer
Copy link
Author

jdemeyer commented Aug 7, 2018

Commit: 73e4365

@embray
Copy link
Contributor

embray commented Aug 8, 2018

comment:4

I thought we were going to do filename_to_bytes or something like that? (I feel like I replied to that idea positively already but it seems maybe my reply was lost).

Should we go ahead and do that, or just accept this change first and update it later?

@vbraun
Copy link
Member

vbraun commented Aug 11, 2018

Changed branch from u/jdemeyer/ticket/26020 to 73e4365

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

No branches or pull requests

3 participants