Re: [sage-devel] Making the transition from user to developer

2018-07-11 Thread Ursula Whitcher
On 7/11/2018 3:19 PM, profgr...@gmail.com wrote: What would be a good way for a Sage user with a basic programming background to learn about Sage development and how codebases are built? Projects ultimately of interest so far are (1) a "show-my-steps" feature for differentiation in Sage or

[sage-devel] Making the transition from user to developer

2018-07-11 Thread profgross
What would be a good way for a Sage user with a basic programming background to learn about Sage development and how codebases are built? Projects ultimately of interest so far are (1) a "show-my-steps" feature for differentiation in Sage or (2) a feature for generating proofs by induction

Re: [sage-devel] Re: How parallel should @parallel be?

2018-07-11 Thread William Stein
On Wed, Jul 11, 2018 at 7:11 AM, Julian Rüth wrote: > Thanks for the feedback so far. It seems that there are pros and cons to all > of the options. > > What about the following: We go with the somewhat random min(8, number of > threads) and print a warning once if "number of threads" > 8

[sage-devel] Re: How parallel should @parallel be?

2018-07-11 Thread Eric Gourgoulhon
Le mercredi 11 juillet 2018 16:11:01 UTC+2, Julian Rüth a écrit : > > Thanks for the feedback so far. It seems that there are pros and cons to > all of the options. > > What about the following: We go with the somewhat random min(8, number of > threads) and print a warning once if "number of

[sage-devel] Re: How parallel should @parallel be?

2018-07-11 Thread Julian Rüth
Thanks for the feedback so far. It seems that there are pros and cons to all of the options. What about the following: We go with the somewhat random min(8, number of threads) and print a warning once if "number of threads" > 8 (telling the user to export SAGE_NUM_THREADS)? Note that this