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 these are quite minor issues, but they are enough to stop me from pursuing issues further.
I'm a C++ developer, so general concepts are not the issue, it is sage/python specific things that I need help with. I propose adding a section to the sage developer guide that address things like: How to setup a testing environment that won't interfere with my installed sage. How to debug code on the command line. How to debug in code in Jupyter. What are the differences between Sage's use of python and vanilla python? Are there tricks to sage development that make it simpler? How to I find the code being called? Which python debugger are best for sage? I can write those sections, but I will need help and direction from the community. My goal is to make it dead easy for people like myself to fix minor problems. Some of the above are probably generic python questions. However, having them addressed here makes it more likely the casual user will contribute. Even if all the doc does is to provide links to python sites, that is helpful. A couple weeks ago I was looking at a latex formatting issue that Samuel Lelievre helped me with (Thanks Samuel), but I wasn't able to trace the code in the debugger. I still want to address that. Regards, Andy -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
