2017-01-17 14:49:09 +0100 | received badge | ● Notable Question (source) |

2013-03-12 13:55:42 +0100 | received badge | ● Popular Question (source) |

2012-10-24 02:50:06 +0100 | received badge | ● Famous Question (source) |

2012-03-13 12:41:47 +0100 | received badge | ● Famous Question (source) |

2012-01-28 04:49:57 +0100 | received badge | ● Notable Question (source) |

2011-11-11 14:38:30 +0100 | received badge | ● Notable Question (source) |

2011-11-03 23:02:20 +0100 | received badge | ● Popular Question (source) |

2011-09-19 10:29:17 +0100 | received badge | ● Popular Question (source) |

2011-07-27 21:04:23 +0100 | marked best answer | callable symbolic expression from python script I am not sure whether your overall goal is worth pursuing. From the surface, it looks like Just for reference, your example can be done in Sage as follows: Using a symbolic function: Using a concrete function: As far as I know, the above functionality has been around for a while without any changes, so I would not be too concerned about the stability of Sage's interface. |

2011-07-27 21:03:41 +0100 | marked best answer | sage-python, matplotlib.pyplot: backends tk and pygtk not recognized Sage is looking for those bindings installed in Sage's copy of python. You can install things in Sage's copy of python by doing "sage -sh" and then whatever you normally would do to install the python bindings. For Sage's matplotlib, the graphical guis are also turned off by default. Define the environment variable: and then reinstall Sage's matplotlib: to compile support for other backends in Sage. |

2011-07-27 21:03:21 +0100 | marked best answer | sage-python, import matplotlib: no module named _tkagg For Sage's matplotlib, the graphical guis are also turned off by default. Define the environment variable: and then reinstall Sage's matplotlib: to compile support for other backends in Sage. |

2011-07-27 21:03:21 +0100 | received badge | ● Scholar (source) |

2011-06-30 13:57:55 +0100 | asked a question | sage-python, matplotlib.pyplot: backends tk and pygtk not recognized I am trying to solve the problem I was having in this question - but since I did a clean sage install since then I figured I would start a new question. I am writing python modules and running them with sage-python (currently, python-2.6.4.p10). I need some plotting capability, both to the screen and plots written to files. My plan is to use matplotlib.pyplot for this (but I will gladly abandon pyplot if it is appropriate).
From the bash prompt with matplotlibrc backend specified as GTKAgg: From the bash prompt with matplotlibrc backend specified as TkAgg: Now, I am running Arch Linux and according to my package manager, pacman, I have I have looked here but I don't see how to get tk8.5-dev since I don't use the Debian repositories (it seems to be available for Ubuntu and Debian). It may be that I simply have an |

2011-06-29 04:38:55 +0100 | received badge | ● Student (source) |

2011-06-28 16:41:40 +0100 | asked a question | sage-python, import matplotlib: no module named _tkagg
I am using Sage's python and trying to import matplotlib.pyplot in order to generate some visual output (to the screen for now, to a file at some point). I understand the backend I should use is TkAgg for this, and I have that set in my matplotlibrc file. When running a short script pleasePlot.py: as I am greeted with absolutely no output. When examining this closer, by running a sage-python (python2.6.4.p10) shell I get the following: I have tried but this does not magically fix the problem. As well, Google seems to not be much help. What do you think?
the file starts out as: so I went searching around ... (more) |

2011-06-27 11:35:48 +0100 | commented answer | How do I get sage to honor my PYTHONPATH environmental variable? Emerson, these are directives specified in the .bashrc or .bash_profile file sitting in your home directory. The best thing for you to do is to learn about the .bashrc file (and the .bash_profile file) in general, then look into what are known as environment variables, which are these PATH things they are talking about. |

2011-06-14 17:16:16 +0100 | commented answer | How do I Pass a tuple as an argument for a multivariate polynomial? What about the efficiency of each/any of the above methods? In particular, is unpacking the dictionary quicker than unpacking the list? |

2011-06-01 17:33:50 +0100 | received badge | ● Supporter (source) |

2011-06-01 17:15:37 +0100 | commented answer | callable symbolic expression from python script I agree that MyFunc is a clone of sage.symbolic.expression.Expression, but I *think* that is what I want here. I am trying to have these symbolic expressions available to a larger system written in python... I am rewriting a large amount of OO Matlab code in python. For better or worse, I am being guided by my earlier design patterns. Is there a deprecation issue with the code I have written? |

2011-06-01 16:48:54 +0100 | received badge | ● Editor (source) |

2011-06-01 16:48:26 +0100 | answered a question | callable symbolic expression from python script Alright, I guess it works this way sometimes (ask question, five minutes later figure out the answer!) Using the information here (Sage tutorial), we can build a This uses the Sage function(...) method as explained in the link. It is clean and I like it. |

2011-06-01 16:21:15 +0100 | asked a question | callable symbolic expression from python script I am trying to obtain a callable symbolic expression from a python script and having a hard time of it. In my python script I would like to have something along the lines of: In the module defining The goal is to keep the client code that constructs, calls, and manipulates objects of type myFunc from knowing about Sage. Perhaps I am misguided, any help would be appreciated. (also, help with the appropriate tags would be, well, helpful) |

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.