py3 print in combinat/designs

[fchapoton]

another step in the direction of print in py3 format

CC: @dimpase

Component: python3

Author: Frédéric Chapoton

Branch/Commit: 9dc1aa2

Reviewer: Dima Pasechnik

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

[fchapoton]

New commits:

d41d844

python3 print in combinat/designs

[fchapoton]

Commit: d41d844

[fchapoton]

Branch: public/20557

[dimpase]

comment:2

What is the purpose of these from future import ? AFAIK python does have a print function (in __builtin__); do you need to change it in a drastic way?

[fchapoton]

comment:3

this ticket is part of a large set of tickets that prepare sage to run with python3
by adapting the syntax of print, which has changed between py2 and py3

the from future import is there to obtain the py3 behaviour in py2

[dimpase]

comment:4

Could you point me to a place in this branch where this import is needed?

[fchapoton]

comment:5

nowhere maybe, but still this is useful as a marker and placeholder that no bad use of print will appear here.

see

https://groups.google.com/forum/#!topic/sage-devel/3bS-Lg5Er9c

and

https://groups.google.com/forum/#!topic/sage-devel/DrMJtNQid6s

The main idea is: looking at all the code of sage and correcting the prints
is not a light task. Let us try to do it only once.

[sagetrac-git]

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

eb4b7bf

python3 in combinat/designs, detail

[sagetrac-git]

Changed commit from d41d844 to eb4b7bf

[dimpase]

comment:7

Replying to @fchapoton:

nowhere maybe, but still this is useful as a marker and placeholder that no bad use of print will appear here.

see

https://groups.google.com/forum/#!topic/sage-devel/3bS-Lg5Er9c

and

https://groups.google.com/forum/#!topic/sage-devel/DrMJtNQid6s

The main idea is: looking at all the code of sage and correcting the prints
is not a light task. Let us try to do it only once.

I just mean that files that do not need this import should not have it.
Note that they also create an extra confusion, as doctsrings still have python2 print() calls.