Re: [sage-devel] Re: Developer guide for casual user

2018-09-24 Thread Erik Bray
On Sun, Sep 23, 2018 at 7:23 PM William Stein wrote: > > On Sun, Sep 23, 2018 at 9:57 AM, Simon King wrote: > > Hi Andy, > > > > On 2018-09-23, Andy Howell wrote: > >> I'd guess the word "tricks" was objectionable. What I meant was > >> techniques like locating the source using funcName? Now tha

Re: [sage-devel] Re: Developer guide for casual user

2018-09-23 Thread Nils Bruin
On Sunday, September 23, 2018 at 7:23:45 PM UTC+2, William wrote: > > However, be warned: I just notice that the anser of sage_getfile(P) is > > wrong (the source file is NOT in local/lib/..., but of course in > > src/sage/rings/... Only the anser for sage_getfile(x) is correct. > > +1 to poi

Re: [sage-devel] Re: Developer guide for casual user

2018-09-23 Thread William Stein
On Sun, Sep 23, 2018 at 9:57 AM, Simon King wrote: > Hi Andy, > > On 2018-09-23, Andy Howell wrote: >> I'd guess the word "tricks" was objectionable. What I meant was >> techniques like locating the source using funcName? Now that I know that >> exists, I can add it to my "practice". Discovering

[sage-devel] Re: Developer guide for casual user

2018-09-23 Thread Simon King
Hi Andy, On 2018-09-23, Andy Howell wrote: > I'd guess the word "tricks" was objectionable. What I meant was > techniques like locating the source using funcName? Now that I know that > exists, I can add it to my "practice". Discovering those though google > searches takes time. I'd rather have a

Re: [sage-devel] Re: Developer guide for casual user

2018-09-23 Thread William Stein
On Sun, Sep 23, 2018 at 8:27 AM, Andy Howell wrote: > I vaguely remember some kind of python sandboxing system, the I'm not sure > if that would apply here. virtualenv. We don't use it for sage dev though. My advise is that you just have a second copy of Sage, unless you are very low on disk sp

Re: [sage-devel] Re: Developer guide for casual user

2018-09-23 Thread Andy Howell
Travis, On 09/21/2018 07:51 PM, Travis Scrimshaw wrote: > 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. Thanks. > > I'm a casual user of sage and python. I know a

[sage-devel] Re: Developer guide for casual user

2018-09-23 Thread Emmanuel Charpentier
Le dimanche 23 septembre 2018 08:18:21 UTC+2, Dominique Laurain a écrit : > > > Travis : "I'm sorry, but that really sounds like "I want to get really > good without practicing". > > My hobby time credit is quite limited and there is a hugge difference > between "without practicing" and good de

[sage-devel] Re: Developer guide for casual user

2018-09-22 Thread Dominique Laurain
Travis : "I'm sorry, but that really sounds like "I want to get really good without practicing". My hobby time credit is quite limited and there is a hugge difference between "without practicing" and good dev time management inducing *awareness* about the main Tools (or how to make good code

[sage-devel] Re: Developer guide for casual user

2018-09-21 Thread Travis Scrimshaw
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

[sage-devel] Re: Developer guide for casual user

2018-09-21 Thread Samuel Lelievre
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