[Yt-dev] Migration to 2.0 being the stable branch

[Matthew Turk]

Awesome!  Hopefully the update will be an easy process -- I think the
only imports that broke are things that aren't from "yt.mods", which
the majority of functionality is in.  I believe that our biggest
problem will actually be people who write things like:

from yt.mods import *
import yt.lagos as L
import yt.raven as R
a = L.EnzoStaticOutput("something")
pc = R.PlotCollection(...)

But, again, hopefully the sweetening of better readability and the
kD-tree (along with the other improvements that have been made along
the way) will help with this.

On Mon, Nov 8, 2010 at 10:15 AM, Stephen Skory <stephenskory at yahoo.com> wrote:
>> Thoughts?
>
>
> Nothing specific, except that I support this idea. I've been bugging Sam to integrate his volume rendering stuff into the development branch (and write docs for it simultaneously), so that stuff may be ready for release by then (Sam?). I would also like to point out that we will have to go through the docs and change the examples, in addition to the conversion rubric Matt wrote about.
>
>
> Stephen Skory
> stephenskory at yahoo.com
> http://stephenskory.com/
> 510.621.3687 (google voice)
>
> _______________________________________________
> Yt-dev mailing list
> Yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>