Why not just version it. Its easy for the handful of people that actually customized their DOT_SAGE/ipython to forward-port their changes. But there is a whole world of hurt lurking for people that don't know about it and suddenly have Sage break because they once started up an old version.
On Wednesday, June 20, 2012 6:18:26 PM UTC+1, jason wrote: > > On 6/20/12 12:12 PM, Volker Braun wrote: > > On Wednesday, June 20, 2012 4:53:24 PM UTC+1, jason wrote: > > > > Also, I changed IPYTHONDIR to ipython-new, instead of ipython-0.12, > > since we hope to update to 0.13 soon. > > > > > > I very much prefer versioned ipython directories. They are not > > compatible across versions. Maybe between 0.12 and 0.13 but why push our > > luck. > > Good point. There was a complete rewrite of IPython between 0.10 and > 0.11. I'll ask on the IPython list if they plan to keep their new > config format, or if it is indeed changing every release. > > In fact, I think it would be better to rename the old IPython config > directory to ipython-0.10 and make the current ipython config simply > ipython. The presumption here is that once people upgrade to the new > version of Sage, they won't be running an old version of Sage (or if > they do, they'll have to fix a few things manually). If the config file > changes again, then rename the current directory to the old version. > That way we aren't creating lots of new directories when we don't need to. > > Jason > > -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
