Opened 23 months ago

Last modified 2 months ago

#28706 new defect

clarify order generation in number fields with bracket syntax

Reported by: kcrisman Owned by:
Priority: minor Milestone: sage-9.5
Component: number fields Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


At this Stackoverflow question, a question arises which boils down (I think) to this interesting comparison.

    sage: K.<a> = NumberField(x^3 - 2)
    sage: Za = ZZ[a]
    sage: OK = K.maximal_order()
    sage: OK.number_field()
    Number Field in a with defining polynomial x^3 - 2
    sage: Za.number_field()
    Number Field in a0 with defining polynomial x^3 - 2 with a0 = a
    sage: OK.number_field() == Za.number_field()

So we don't seem to have a way to compare what appear to be isomorphic number fields that are output with only a trivial-looking difference to the user.

I won't suggest a fix that would make this work - perhaps it is technically impossible. But at least the documentation at generating orders that advertises the syntax ZZ[a] should be strongly updated to make it clear how misleading this will be.

Change History (5)

comment:1 Changed 21 months ago by embray

  • Milestone changed from sage-9.0 to sage-9.1

Ticket retargeted after milestone closed

comment:2 Changed 17 months ago by mkoeppe

  • Milestone changed from sage-9.1 to sage-9.2

Batch modifying tickets that will likely not be ready for 9.1, based on a review of the ticket title, branch/review status, and last modification date.

comment:3 Changed 13 months ago by mkoeppe

  • Milestone changed from sage-9.2 to sage-9.3

comment:4 Changed 7 months ago by mkoeppe

  • Milestone changed from sage-9.3 to sage-9.4

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

comment:5 Changed 2 months ago by mkoeppe

  • Milestone changed from sage-9.4 to sage-9.5
Note: See TracTickets for help on using tickets.