Changes between Version 47 and Version 60 of Ticket #17898


Ignore:
Timestamp:
03/10/15 23:17:18 (5 years ago)
Author:
aschilling
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17898

    • Property Status changed from needs_work to positive_review
    • Property Summary changed from Removal of wrong stopgap to Move of stopgap to user level
    • Property Commit changed from d3de7cf960cb38e03d69d3e4b8951bcc9ddd830a to ec3405e8913eba4c7ce55b7abe69a4829144a844
  • Ticket #17898 – Description

    v47 v60  
    1 As documented in #17548 there are no reported bugs related to IntegerListsLex. All cases listed on that ticket have non-valid input (as documented in the code).
     1Currently the stopgap on IntegerListsLex pops up in many functions and classes, where IntegerListsLex is used in the correct parameter range. This ticket moves the stopgap to the user level and implements further checks on the validity of the input parameters for IntegerListsLex.
    22
    3 Since the stopgap is not related to any bug and shows up in completely unrelated code, where IntegerListsLex is correctly used, for example
     3Here are examples where the message currently appears without reference to IntegerListsLex:
    44{{{
    55sage: K = crystals.KirillovReshetikhin(['D',4,1],1,1)
     
    2020Partitions of 3 having parts less than or equal to 2
    2121}}}
    22 it should be moved to the user interface level, which is done in this ticket.