Revision history [back]

Hi, i don't know if this qualifies as best practice, but a workflow i've used (to collaborate w/other people) was to put the code in a gitlab repository (which provides ATM free and private hosting, and a very good quality interface), and then to pull it from a CoCalc project. (i don't remember if you need an upgraded account for this; i have one). anyway, the convenience of this approach is that you can work from anywhere with internet and you don't need sagemath installed in all machines..

for the jupyter notebooks/usual scripts concern, i find the former very practical for playing around with a small chunk of code, although it's better to pass to the latter for organizing the code into a usual python module. (i.e. do not pay attention to version controlling the .ipynb file, whose diff is rather messy, but rather the .py scripts).

hope that helps!

Hi, i don't know if this qualifies as best practice, but a workflow i've used (to collaborate w/other people) was to put the code in a gitlab repository (which provides ATM free and private hosting, and a very good quality interface), and then to pull it from a CoCalc project. (i don't remember if you need an upgraded account for this; i have one). anyway, the convenience of this approach is that you can work from anywhere with internet and you don't need sagemath installed in all machines..

for the jupyter notebooks/usual scripts concern, i find the former very practical for playing around with a small chunk of code, although it's better to pass to the latter for organizing the code into a usual python module. (i.e. do not pay attention to version controlling the .ipynb file, whose diff is rather messy, but rather the .py scripts).messy).

hope that helps!