[yt-dev] What needs to be done for a 3.3 release?

[John ZuHone]

I'd be in favor of a "conda or pip" solution as opposed to a "conda"-only solution for us. With the binary wheels we can support OSX and Windows without much issue, and for Linux building from source works most of the time.

That said, before we standardized this it would be good if we had it so that pip downloaded all of the dependencies when you did "pip install yt". I realize that this is not as simple as it sounds, and that we've looked at this already, but we should try again I think.

In my opinion the install script is getting to be a lot of trouble, which is why we should at least start the process of moving away from it (to a certain extent we have).

John ZuHone
Harvard-Smithsonian Center for Astrophysics 

60 Garden St., MS-67
Cambridge, MA 02138
(w) 617-496-1816
(m) 781-708-5004
jzuhone at cfa.harvard.edu
jzuhone at gmail.com
http://www.jzuhone.com

> On Jan 15, 2016, at 8:41 AM, Matthew Turk <matthewturk at gmail.com> wrote:
> 
> Hi Nathan,
> 
> (I'll reply to Andrew a bit later once I've thought it over.)
> 
> I'd strongly campaign against unifying the two scripts right now, if
> ever.  I don't like that we have two either, but I don't think we
> should make this part of the 3.3 release cycle, just because it's yet
> another major potential disruption.  It would be nice to work out a
> way to migrate nicely to conda, but maybe we should hold off until we
> have infrastructure in place for our own conda package builds?
> 
>> On Thu, Jan 14, 2016 at 5:20 PM, Nathan Goldbaum <nathan12343 at gmail.com> wrote:
>> 
>> 
>>> On Thu, Jan 14, 2016 at 1:45 PM, Andrew Myers <atmyers2 at gmail.com> wrote:
>>> 
>>> Dear yt developers,
>>> 
>>> yt version 3.2 was released back in July of 2014. Since then, there have a
>>> been a number of cool new features added (good work, everyone!), and it
>>> would be nice to get them into a stable release. However, there are a few
>>> major things that need to be done before that can happen. First, there are a
>>> number of outstanding issues related to the volume render refactor that need
>>> to be addressed before 3.3 can be released. Additionally, version 3.3 will
>>> include unstructured mesh visualization support, and there is some more work
>>> Matt and I need to do before that is ready. Other than those things, though,
>>> is there anything I'm leaving out that people want to get in before version
>>> 3.3 is released?
>> 
>> 
>> I would like to see the install script situation resolved. In particular, I
>> think get_yt.sh and install_script.sh should be merged, and users
>> should be able to choose at install time whether or not they want a
>> source-based install or a miniconda-based install.
>> 
>>> 
>>> 
>>> Thanks for your time,
>>> Andrew
>>> 
>>> _______________________________________________
>>> yt-dev mailing list
>>> yt-dev at lists.spacepope.org
>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> 
>> 
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20160115/ae7ea776/attachment.htm>
-------------- next part --------------
_______________________________________________
yt-dev mailing list
yt-dev at lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org