#5994: singular.version() yields an error when first called, has no doctest, and
has a strange output imo
------------------------+---------------------------------------------------
Reporter: SimonKing | Owner: was
Type: defect | Status: new
Priority: major | Milestone: sage-4.0
Component: interfaces | Keywords: singular version
------------------------+---------------------------------------------------
Comment(by AlexGhitza):
Replying to [comment:3 SimonKing]:
>
> "Upstream" answered, and it seems that the problem is fixed in the
official release.
>
> I could verify that on the server in Oberwolfach, the error does not
occur in Singular 3-1-0, but it ''does'' occur in Oberwolfach in Singular
3-0-4 (as being part of Sage). Opinions?
We can probably wait until after Sage Days 15 for this?
> But there still remains the question if {{{singular.version()}}} ought
to return a tuple of integers, rather than a lengthy string with all build
informations.
My personal preference would be for it to return a tuple of integers, but
we could give it an optional argument {{{with_build_info=True}}} (or
{{{verbatim=True}}} or something similar) to make it return the lengthy
string.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5994#comment:4>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
