Closed edd8e884-f507-429a-b577-5d554626c0fe closed 5 years ago
New commits:
99419a8 | #28480 UniqueRepresentation for OEISSequence |
Commit: 99419a8
For what is worth, the next step is to have a lazy OEISSequence
that could exist as soon as its ID is known, and fetch data on the internet only when needed, not during __init__
. Then, we will be able to use local data as well (e.g. for first terms and name). Then, we will have some overflow detection, that will advise the user who uses oeis online intensively to fetch some data once for all. This is how i currently plan to split the various tickets. The global goal is to save bandwidth, protect oeis servers from brute force searches, and allow faster searches. I plan to push a step only when the previous is merged to avoid rebasing between tickets.
Reviewer: Frédéric Chapoton
ok, good to go
moving milestone to 9.0 (after release of 8.9)
Changed branch from u/tmonteil/let_oeis_sequences_have_unique_representation to 99419a8
Changed commit from 99419a8
to none
Follow-up: #28627 (lazy OEIS sequences).
While innocent looking, this feature is a first step towards bandwidth saving. At least, it reduces overall code length.
CC: @mo271 @videlec @seblabbe
Component: combinatorics
Author: Thierry Monteil
Branch:
99419a8
Reviewer: Frédéric Chapoton
Issue created by migration from https://trac.sagemath.org/ticket/28480