-
-
Notifications
You must be signed in to change notification settings - Fork 453
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: several string conversion fixes #24223
Comments
comment:1
With this, plus a few other small fixes (including fixes from other existing tickets merged in) I was able to get the Sage REPL up and |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:3
Rebased on current version of #24222. |
comment:4
Something is wrong: there are still the files |
comment:5
This is again a ticket with many small independent changes where a "partial positive review" like what I proposed on #24025 would make sense. I didn't like how we handled that, so how should we proceed here? |
comment:6
Replying to @jdemeyer:
Oops--part of the problem here is I'm moving between two different working trees, one for Python 2 and one for Python 3, so it can get confusing. I'll clean this up. |
comment:7
Replying to @jdemeyer:
I'd be fine if you proposed your changes and tossed it back to me as "needs review", rather than going immediately to "positive review". |
comment:8
It seems strange to me to use
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:12
Is this needs_review again? |
comment:13
Yeah, IIRC this was just a bunch of miscellaneous string conversions from some other tickets, but redone using the |
comment:14
3 failing doctests in integer.pyx |
comment:16
Interesting--when I added So I see at least three options:
I lean towards 1. but I'm open to ideas. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Jeroen Demeyer |
comment:34
This does not work:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:36
import corrected |
Changed branch from public/python3-trac24223 to u/embray/python3/string-fixes |
comment:37
I rebased and squashed some of these changes. New commits:
|
comment:38
|
comment:39
Volker, did you use the latest branch ? |
comment:40
He didn't. Setting this back to positive review since this otherwise fixes Jeroen's issue. |
Changed branch from u/embray/python3/string-fixes to |
This fixes several (hardly exhaustive) string conversions around Sage such that functions and methods that returned
str
on Python 2 also returnstr
on Python 3 (and the same for functions and methods that takestr
as arguments) using the new string utilities from #24222.This also incorporates/replaces the fixes from #23812.
CC: @fchapoton @jdemeyer
Component: python3
Author: Erik Bray
Branch/Commit:
e9a582e
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/24223
The text was updated successfully, but these errors were encountered: