#10358: The sloane_find command is now completely broken
---------------------------+------------------------------------------------
Reporter: was | Owner: tmonteil
Type: defect | Status: closed
Priority: critical | Milestone: sage-4.6.1
Component: combinatorics | Resolution: duplicate
Keywords: | Author:
Upstream: N/A | Reviewer:
Merged: | Work_issues:
---------------------------+------------------------------------------------
Changes (by tmonteil):
* cc: sage-combinat, was (added)
* owner: sage-combinat => tmonteil
Comment:
Hi,
the aim of #10056 was to migrate every url in sage that was dealing with
Sloane's database at once (not only `sloane_find()`), hence this is not
really a duplicate. The issue here is that oeis changed their html
templates, so the sage parsers are not working anymore. I just coded a new
parser, which you can see working on the combinat repository
(`sloane_new_website_parsers-tm.patch`).
I added the more atomic functions in `sage/databases/sloane.py` (the
documentation still needs to be fixed):
- `sloane_discover()` which discovers which sequences correspond to some
list of integers.
- `sloane_first_terms()` which returns the first terms of the sequence.
- `sloane_description()` which returns the one line description of the
sequence.
I don't really know what to do with the broken functions:
- `parse_sequence()` is completely dead and now useless. Should it now
raise a deprecation warning ?
- `sloane_sequence()` and `sloane_find()` are broken, but maybe some
users still need them, should i make them working again as a combination
of the first 3 functions ?
Also, maybe all those functions should be renamed by replacing sloane by
oeis ? This may be too early since i guess most people know more about
Sloane than about oeis. In such a case, what is the procedure/convention
to ensure backward compatibility ?
At the end, we could have a daily crontab to check when the oeis changes
its html template, and adapt the parsers accordingly. Better, we could ask
them to provide an online standard query system, but if i understand a
discussion in the nmbrthry mailing-list, this may not be their whish.
Ciao,
Thierry
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10358#comment:3>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
