#8360: Add an interface to Jean-Eric Pin's Semigroupe package
-------------------------------------------------+-------------------------
Reporter: nthiery | Owner: nthiery
Type: enhancement | Status:
Priority: major | needs_work
Component: algebra | Milestone: sage-
Keywords: Semigroupes | feature
Authors: Florent Hivert, Jean-Eric | Resolution:
Pin, Nicolas M. Thiéry | Merged in:
Report Upstream: N/A | Reviewers:
Branch: | Work issues:
Dependencies: | Commit:
| Stopgaps:
-------------------------------------------------+-------------------------
Comment (by nthiery):
Replying to [comment:13 slabbe]:
> Replying to [comment:12 nthiery]:
> > The next step is actually just to make a branch out of the patch.
> you mean a git branch?
Yup.
> which patch? is it finite_semigroup-nt.patch ?
> I don't see how this patch uses semigroupe.
trac_8360_semigroupe-interface-nt.patch
> > I am not sure about actually getting this branch into Sage until
> > Semigroupe will be fixed one way or the other to support several
> > semigroups simultaneously.
> I think I don't agree. I think the goal of the actual ticket #8360
> is to make the actual semigroup into sage as it is. semigroupe was
> written for something no? Let's first make this available!
Indeed, the interface was written for something. But in practice, even
if I spent quite some time on it, I am actually seldom using it
because that misfeature is making it relatively unusable (at least in
my use-cases).
> Then I suggest to open a ticket showing with sage command line code
> illustrating how the bug for creating two semigroup simultaneously
> is obtained. The new ticket would ask for an upstream fix.
That's an option. If you are convinced that:
#. At some point not to far in the future the bug will be fixed
upstream (upstream meaning possibly us taking the time to do the
fix).
#. The current code won't need serious interface change then.
Then let's go ahead. Otherwise I am a bit reluctant to put in Sage
some code that we might need to remove (because unused) or change a
lot later on.
At the end of the day, this would actually be best handled by putting
the interface code in the spkg and not in the Sage library. I haven't
checked how hard/easy it would be to handle.
Cheers,
Nicolas
--
Ticket URL: <http://trac.sagemath.org/ticket/8360#comment:14>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
