Since Travis answered, I'll also throw in some answers for variety (I
mainly going to mention things that are complementary)...
On Fri, Sep 21, 2018 at 9:29 AM, Andy Howell wrote:
> How to setup a testing environment that won't interfere with my
> installed sage.
I would *always* install a compl
Samuel,
I am the personification of preoccupations upon preoccupations. No problem.
My meager attempt lead me to pynac as well, though not into the library
itself. I do know C++, so maybe I can make some progress there.
I cloned pynac. There are some dependencies to work out to get it to
build.
Hi Andy,
It would be great to improve our methodologies for recruiting/training
new contributors and developers, and I am happy to hear you are willing to
work on this.
I'm a casual user of sage and python. I know a little of both, but far
> far from expert. There have been a number of very
Hi Andy, thanks for your offer to make it easier to contribute to Sage
by adding tips to the developer guide. I'm sure the community will
jump in to help where needed. Regarding the latex formatting issue
you reported three weeks ago, I opened a ticket to track progress:
- Sage Trac ticket 26337
Andy,
three weeks ago, after the partial exploration discussed on this list,
I switched to other preoccupations and forgot to get back to this.
To recap and go a little further, here is how I would describe
the issue and some steps to explore it:
Current:
sage: h = e^-x
sage: latex(h)
+1 from me too.
On Fri, Sep 21, 2018 at 6:08 PM Matthias Koeppe
wrote:
>
> +1 on splitting it out as a standalone Python package. With a bit of luck, a
> new set of contributors for it can be found that way.
>
> On Friday, September 21, 2018 at 11:06:47 AM UTC-4, Erik Bray wrote:
>>
>> On Fri, Se
+1 on splitting it out as a standalone Python package. With a bit of luck,
a new set of contributors for it can be found that way.
On Friday, September 21, 2018 at 11:06:47 AM UTC-4, Erik Bray wrote:
>
> On Fri, Sep 21, 2018 at 4:29 PM Nils Bruin >
> wrote:
> >
> > On Friday, September 21, 20
I'm a casual user of sage and python. I know a little of both, but far
far from expert. There have been a number of very minor bugs that I
could fix, but was stymied because I don't know, or have forgotten, how
to debug sage code, how to find the code be called etc. To the regular
sage developer th
On Fri, Sep 21, 2018 at 4:29 PM Nils Bruin wrote:
>
> On Friday, September 21, 2018 at 1:46:47 AM UTC-7, Erik Bray wrote:
>>
>> There is a cool module in sage called sage.misc.explain_pickle, which
>> is useful for helping to understand and debug how non-trivial objects
>> in Sage are pickled and
On Friday, September 21, 2018 at 1:46:47 AM UTC-7, Erik Bray wrote:
>
> There is a cool module in sage called sage.misc.explain_pickle, which
> is useful for helping to understand and debug how non-trivial objects
> in Sage are pickled and unpickled.
>
> I am adding another testimonial on the u
On Fri, Sep 21, 2018 at 3:00 PM Jeroen Demeyer wrote:
>
> It must be said that I found this tool quite valuable. When unpickling
> goes wrong, it is typically not easy to find out why and explain_pickle
> does help with that.
>
> That being said, if nobody wants to maintain it, it has to go (with
It must be said that I found this tool quite valuable. When unpickling
goes wrong, it is typically not easy to find out why and explain_pickle
does help with that.
That being said, if nobody wants to maintain it, it has to go (with
praise, as you said)...
--
You received this message because
On Fri, Sep 21, 2018 at 01:40:38PM +0100, dimp...@gmail.com wrote:
[...]
> IMHO we don't want such legacy things as standard...
Agreed. But how should we deal with testing networkx ?
Ciao,
Thierry
>
> Dima
>
> --
> You received this message because you are subscribed to the Google Groups
>
On Fri, Sep 21, 2018 at 02:27:13PM +0200, Thierry wrote:
> Hi,
>
> on the way to upgrading networkx, i noticed that the source code contains
> tests, but we do not ship any spkg-check script for that (yet).
>
> However, the check process requires nose, which is an optional package
> (note that ne
Hi,
on the way to upgrading networkx, i noticed that the source code contains
tests, but we do not ship any spkg-check script for that (yet).
However, the check process requires nose, which is an optional package
(note that networkx is standard). Is there a way to declare "check
dependencies" (e.
On Fri, Sep 21, 2018 at 11:42 AM William Stein wrote:
>
>
>
> On Fri, Sep 21, 2018, 1:07 AM Frédéric Chapoton wrote:
>>
>> Hello,
>>
>> Apparently, people can "donate to the SAGE foundation" using this link :
>> https://www.washington.edu/giving/make-a-gift/?page=make&Code=MATSAG
>>
>> which is
On Fri, Sep 21, 2018, 1:07 AM Frédéric Chapoton
wrote:
> Hello,
>
> Apparently, people can "donate to the SAGE foundation" using this link :
> https://www.washington.edu/giving/make-a-gift/?page=make&Code=MATSAG
>
> which is advertised here : http://www.sagemath.org/development-ack.html
>
> Who i
There is a cool module in sage called sage.misc.explain_pickle, which
is useful for helping to understand and debug how non-trivial objects
in Sage are pickled and unpickled.
However, it's a big, fairly complicated module which carries quite a
bit of technical debt with it, and relatively little o
Hello,
Apparently, people can "donate to the SAGE foundation" using this link :
https://www.washington.edu/giving/make-a-gift/?page=make&Code=MATSAG
which is advertised here : http://www.sagemath.org/development-ack.html
Who is in charge ? How much money is collected (I would guess almost
noth
19 matches
Mail list logo
