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 print in libs folder #20556

Closed
fchapoton opened this issue May 4, 2016 · 22 comments
Closed

py3 print in libs folder #20556

fchapoton opened this issue May 4, 2016 · 22 comments

Comments

@fchapoton
Copy link
Contributor

a small step towards python3 print

Component: python3

Author: Frédéric Chapoton

Branch/Commit: 6836c5c

Reviewer: Jeroen Demeyer

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

@fchapoton fchapoton added this to the sage-7.2 milestone May 4, 2016
@fchapoton
Copy link
Contributor Author

Commit: 7c59df3

@fchapoton
Copy link
Contributor Author

Branch: public/20556

@fchapoton
Copy link
Contributor Author

New commits:

7c59df3python3 print in libs

@jdemeyer
Copy link

jdemeyer commented May 4, 2016

Reviewer: Jeroen Demeyer

@jdemeyer
Copy link

jdemeyer commented May 4, 2016

comment:2

positive_review if the bot gives the green light.

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 4, 2016

Branch pushed to git repo; I updated commit sha1. New commits:

5f3ec6eoops, forgot one print to python3

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 4, 2016

Changed commit from 7c59df3 to 5f3ec6e

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 5, 2016

Changed commit from 5f3ec6e to 468c1dd

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 5, 2016

Branch pushed to git repo; I updated commit sha1. New commits:

468c1ddpython3 print in libs, details

@jdemeyer
Copy link

jdemeyer commented May 5, 2016

comment:5

Why the last commit? Isn't mpmath supposed to be system-independent?

@fchapoton
Copy link
Contributor Author

comment:7

you mean the abs tol ? I guess I removed a print that was truncating the numerical value.
Should I instead

  • put back a print ?
  • replace by the correct numerical value ?

@jdemeyer
Copy link

jdemeyer commented May 5, 2016

comment:8

replace by the correct numerical value ?

Of course.

@jdemeyer
Copy link

jdemeyer commented May 5, 2016

comment:9

The # tol is stuff is meant for system-dependent doctests. Not for "I am too lazy to write all the digits". Especially for things where it is a feature that they are system-independent.

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 5, 2016

Changed commit from 468c1dd to 6836c5c

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented May 5, 2016

Branch pushed to git repo; I updated commit sha1. New commits:

6836c5cpython3 print in libs, replace by correct numerical value instead of abs tol

@fchapoton
Copy link
Contributor Author

comment:11

done

@jdemeyer
Copy link

jdemeyer commented May 5, 2016

comment:12

Let's see what the patchbot says...

@jdemeyer
Copy link

jdemeyer commented May 5, 2016

comment:13

Won't the changes to src/sage/libs/readline.pyx break the doctest since you replaced print a,b by print(a,b).

@fchapoton
Copy link
Contributor Author

comment:14

no, because this is in the code, not in the doc, and we have the future import

@jdemeyer
Copy link

jdemeyer commented May 5, 2016

comment:15

I see... so there is really a big difference between changes in the code and in the doctests.

If the bot gives the green light, you can set this to positive_review.

@fchapoton
Copy link
Contributor Author

comment:16

ok, bot has turned green.

@vbraun
Copy link
Member

vbraun commented May 19, 2016

Changed branch from public/20556 to 6836c5c

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