Le samedi 7 mai 2016 07:30:42 UTC+2, john_perry_usm a écrit :
>
> I'm sorry. I got the name mixed up; the function you want to look at is
> sba(), not dstd() (which is something experimental of mine that never saw
> the light of day).
>
> http://www.singular.uni-kl.de/Manual/latest/sing_39
I'm sorry. I got the name mixed up; the function you want to look at is
sba(), not dstd() (which is something experimental of mine that never saw
the light of day).
http://www.singular.uni-kl.de/Manual/latest/sing_391.htm#SEC430
Because my copy of Singular is a little... "tinkered with" I'
2016-05-03 09:59:05 UTC-5, Nicolas M. Thiéry:
> Tangentially to the recent discussion about modularity of the Sage
> library and support for packages on top of Sage, I have started
> writing some notes about the different workflows that have been used
> to develop and share code, either "on
Hello all!
My name is Rebecca Lauren Miller, I just finished my first year at Saint
Louis University pursing my Ph.D. in Mathematics. I will be working with
Ben Hutz and Paul Fili to increase the functionality of moduli space. I'm
looking forward to a summer filled with research! Thank you the
Hi Vincent,
I would add to your list:
* when exporting to pdf, the LaTeX format of the output cells is lost (cf.
https://groups.google.com/d/msg/sage-support/Pt_r9Ct-31w/MWkRz1DVBwAJ)
* the menu of JSMol 3D plots is not accessible
Best wishes,
Eric.
--
You received this message because you
Le vendredi 6 mai 2016 15:07:48 UTC+2, john_perry_usm a écrit :
>
>
> One of us misunderstands the other. Here's what I'm saying:
>
>- Singular's std() is neither an F4- nor F5-style algorithm; it is a
>traditional, Buchberger algorithm that uses a modified Gebauer-Möller pair
>sele
Is it strictly needed, no. However, it allows us to be compatible with
Python3 and it helps prevent anyone in the future from adding code that is
only works in Python2 wrt print statements. Furthermore, most of the
docstrings can be made 2/3 compliant and don't need "fancy" print_function
st
Le vendredi 6 mai 2016 14:38:10 UTC+2, Nicolas M. Thiéry a écrit :
>
> On Wed, May 04, 2016 at 05:56:36AM -0700, Eric Gourgoulhon wrote:
> >Thank you Nicolas for this page which is very instructive.
>
> :-)
>
> >I've added some comments on SageManifolds workflow.
>
> Yes, I have seen
I already commented on one of these tickets that I do not understand why
`from __future__ import print_function`
is needed everywhere.
Indeed, most modules do not do nontrivial printing anywhere, except perhaps
docstrings
(and the latter are not affected by that import anyway).
Dima
On Tuesday,
On Wednesday, May 4, 2016 at 11:58:13 PM UTC-5, parisse wrote:
> Le mercredi 4 mai 2016 23:00:23 UTC+2, john_perry_usm a écrit :
>>
>> Unfortunately Roman doesn't mention on that page whether he used
>> Singular's std() or dstd(). The numbers look vaguely std()ish to me (i.e.,
>> when I compute
On Wed, May 04, 2016 at 05:56:36AM -0700, Eric Gourgoulhon wrote:
>Thank you Nicolas for this page which is very instructive.
:-)
>I've added some comments on SageManifolds workflow.
Yes, I have seen this; and commented on one of them. Stuff to discuss
at some point, e.g. the upcoming Sa
On Wed, May 4, 2016 at 10:07 PM, Johan S. R. Nielsen
wrote:
> Michael Orlitzky writes:
>> I have a matrix m... how come,
>>
>> * m.rank gives me bullshit
>> * m.rank() works
>> * m.T() crashes
>> * m.T works?
>
> This is in my mind the most compelling reason to phase out properties in
> Sa
Hi Volker,
On 2016-05-05, Volker Braun wrote:
> Thats an upstream bug...
Yes, but why does it occur in the Sage library with my extension class
but not with other extension classes in the Sage library?
By the way, the problem has disappeared in the meantime. Namely, there
was another warning:
13 matches
Mail list logo
