Why would someone use .sage vs .py? What's recommended? What are the pros and cons? There are questions people ask like: "This can be done in Sage but I can't do it in my python file?" Why would they do anything in python if they could just do it in Sage?
Sage is a (very, very big) python library, and it does not (natively) run on Windowz. "Pure" python is smaller, much more lightweight and easier to install and run.
Just in case, note that .sage and .py are file extensions. In fact, Sage internally "preparses" every .sage file and converts it into .py file. So in particular, if you have a file named f.sage, then do not keep a file named f.py in the same directory, as Sage would overwrite it!
Yes, I am looking for more of a qualitative analysis. The Developer's Guide gives the example of creating new directories and storing python files. Why would it do so if .sage files work just as well without the added issue of importing modules? Is it possible that the Python files can be reused elsewhere? I know that in different situations there is more than one way to solve a problem, I'm wondering why I would ever do things with .py files.
To perhaps help with the response, here is a question which highlights something .sage files can't do, but .py files can: http://ask.sagemath.org/question/1520/python-thing-that-doesnt-work-in-sage-works-in
Asked: 2012-09-27 00:37:21 +0200
Seen: 711 times
Last updated: Sep 27 '12
Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
