modernize sage.rings.real_mpfr

[videlec]

The current sage.rings.real_mpfr deals with arbitrary precision floating-point numbers (using mpfr). This is the default "real field" in many places in Sage even though it is often wiser to use intervals or balls. We perform some cosmetic changes to sage.rings.real_mpfr to emphasize the fact that the module deals with floating-point approximations of real numbers and not genuine reals. These modifications touch a lot of files and involve deprecation of widely used names.

See also the introduction of a genuine real field class in #24456 for another motivation.

step 1

• Move create_RealField to real_field.py #24511: move the class factory create_RealField in real_field.py
• Change string representation of RealField #24523: change string representation
• rename RealField/RealNumber #24524:
  • RealField -> RealFloatingPointField_factory
  • RealField_class -> RealFloatingPointField
  • RealNumber -> RealFloatingPoint
• deprecate is_RealNumber, is_AlgebraicNumber, is_RealIntervalFieldElement, ... #24525: deprecate is_RealNumber(x) and is_RealField(x) in favour of isinstance(x, RealFloatingPoint) and isinstance(x, RealFloatingPointField)

step 2

• Deprecate RR and Reals and use RFF (or RFPF?) as the standard name for RealFloatingPointField(53)?
• more documentation.

---

for complex numbers, see #24489.

Component: basic arithmetic

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

[rwst]

Dependencies: #24456

[rwst]

Author: Ralf Stephan

[rwst]

Changed branch from #24456 to none

[rwst]

comment:2

In real_mpfr.pyx do you mean to rename cpdef RealField(int prec=53,...) or cdef class RealField_class?

[rwst]

Branch: u/rws/rename_sage_rings_real_mpfr_realfield

[rwst]

comment:6

This commit changes 164 files. Preliminary testing passes in rings and src/doc. There might be subtle errors introduced in the documentation. Let's try the patchbots.

---

New commits:

62d2d21	24456: class for the field of real numbers
71f9fd0	24457: bulk rename RealField --> RealFloatingPointField

[rwst]

Commit: 71f9fd0

[rwst]

comment:7

Ah I forgot the string representation part.

[rwst]

comment:8

Sorry, I was pretty sure I excluded real_field.py.

[rwst]

Changed branch from u/rws/rename_sage_rings_real_mpfr_realfield to none

[rwst]

Changed commit from 71f9fd0 to none

[rwst]

Branch: u/rws/24457-1

[rwst]

Commit: 8bdf66b

[rwst]

comment:10

After changing the string representation as well:
223 files changed, 1493 insertions(+), 1493 deletions(-). I don't have hopes this gets through, except maybe in a beta of its own.

---

New commits:

62d2d21	24456: class for the field of real numbers
8bdf66b	24457: rename sage.rings.real_mpfr.RealField

[jdemeyer]

Replying to @videlec:

• change the name of RealField/RealField_class to RealFloatingPointField/RealFloatingPointField_class

Do we still need the old RealField given that it's no longer used after #24456?

[rwst]

Changed branch from u/rws/24457-1 to u/rws/24457-2

[rwst]

New commits:

3c7f16e

24457: rename sage.rings.real_mpfr.RealField

[videlec]

comment:41

Let us do that incrementally (ie each subtask in ticket). It will simplify review and merging. Though I would feel much more confortable if the whole task would be actually closed within the next stable release.

[videlec]

comment:42

Replying to @videlec:

Replying to @rwst:

The deprecation of is_RealNumber(x)/is_RealField(x) in favor of isinstance can be done independently of the renaming. Separate ticket to come.

Good idea!

Though it would be better to first change the names:

• RealField -> RealFloatingPointField_factory
• RealField_class -> RealFloatingPointField
• RealNumber -> RealFloatingPoint
  to avoid passing twice on the same lines.

[rwst]

comment:48

Rebased on the remaining dependency.

[rwst]

comment:49

OOps wrong ticket.

[videlec]

Changed dependencies from #24511 to none

[videlec]

comment:51

update milestone 8.3 -> 8.4