Changes between Initial Version and Version 25 of Ticket #17898
- Timestamp:
- 03/08/15 01:26:32 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #17898
-
Property
Status
changed from
new
toneeds_review
-
Property
Authors
changed from
Anne Schilling
toTravis Scrimshaw, Anne Schilling
- Property Cc vdelecroix jdemeyer added
-
Property
Branch
changed from
to
public/combinat/fix_bad_stopgap-17898
-
Property
Reviewers
changed from
Travis Scrimshaw
toTravis Scrimshaw, Anne Schilling
- Property Keywords stopgap partitions added
-
Property
Commit
changed from
to
2f7a90d8419ca8d2202b3cb31290e58194f666e3
-
Property
Status
changed from
-
Ticket #17898 – Description
initial v25 1 As documented in http://trac.sagemath.org/ticket/17548 there are no reported bugs related to IntegerListsLex. All cases listed on that ticket have non-valid input (as documented in the code). 1 As documented in http://trac.sagemath.org/ticket/17548 there are no reported bugs related to IntegerListsLex. All cases listed on that ticket have non-valid input (as documented in the code). 2 2 3 3 Since the stopgap is not related to any bug and shows up in completely unrelated code, where IntegerListsLex is correctly used, for example … … 20 20 Partitions of 3 having parts less than or equal to 2 21 21 }}} 22 it should be removed. 23 24 Instead, either a check should be added to the code to check the user input or the IntegerListsLex code should be extended to allow for all input. 22 it should be moved to the user interface level, which is done in this ticket.