py3: some work on modular/modform_hecketriangle/

[fchapoton]

CC: @tscrim

Component: python3

Author: Frédéric Chapoton

Branch/Commit: e765ca6

Reviewer: Travis Scrimshaw

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

[fchapoton]

New commits:

fc1bea7

py3: some work on modular/modform_hecketriangle/

[fchapoton]

Commit: fc1bea7

[fchapoton]

Branch: u/chapoton/26967

[sagetrac-git]

Changed commit from fc1bea7 to 580be8f

[sagetrac-git]

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

580be8f

harden one doctest in modform_hecketriangle

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

e765ca6

py3: some work on modular/modform_hecketriangle/

[sagetrac-git]

Changed commit from 580be8f to e765ca6

[fchapoton]

comment:4

green bot, please review.

I have some doubts on the use of SagePrettyPrinter instead of pprint.pformat. In particular, one is forced to import the necessary stuff inside the _repr_ to avoid importing IPython at startup. But Volker said once that one should avoid pprint.pformat, without telling what to do instead.

[tscrim]

comment:5

From #26628, it seems that SagePrettyPrinter is not working either. So I want to wait on this ticket until we can figure out #26628.

[fchapoton]

comment:6

I would argue that here we will only use the pretty printer on a dict with keys all of the same nature (elements in the same ring), hence that should always be comparable. So it should be ok.

The phenomenon of impredictibility seen in #26628 comes from the comparison of letters and numbers.

Would you prefer to use pprint.pformat ?

[tscrim]

Reviewer: Travis Scrimshaw

[tscrim]

comment:7

No, this will be fine.

[vbraun]

Changed branch from u/chapoton/26967 to e765ca6