<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I’m happy to devote effort for the rest of this week and next to finish the Python 3 stuff up. <div class=""><br class=""></div><div class="">Kacper, where do we stand on Python 3 testing?</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 9, 2015, at 2:16 PM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com" class="">nathan12343@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Jul 9, 2015 at 11:12 AM, John ZuHone <span dir="ltr" class=""><<a href="mailto:jzuhone@gmail.com" target="_blank" class="">jzuhone@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We do have one blocker, at least from my point of view. At the moment I am -1.<br class="">
<br class="">
We have done a lot of work to get a single yt codebase for Python 2 and 3, but we have not (to my knowledge) had a single test run where all tests are passing under Python 3, including answer tests.<br class="">
<br class="">
Since the Python 3 stuff is everywhere in the code, we need to verify that all the tests pass (I bet they won’t just yet) before we release.<br class="">
<br class="">
Also, we don’t yet know if “yt update” and “yt instinfo” will work under Python 3 (though I’m happy to find out).<br class=""></blockquote><div class=""><br class=""></div><div class="">I brought this up while talking to Britton earlier. I agree that ideally the python3 stuff would need to be shored up for 3.2, including full testing.</div><div class=""><br class=""></div><div class="">That said, one way to get around this is to say 3.2 has preliminary beta-level support for python3, but that will support will come in 3.3 (or even in a 3.2.1 release).</div><div class=""><br class=""></div><div class="">If we can quickly-ish get full python3 support then great, I just don't want to be blocked on developer time for a while.</div><div class=""><br class=""></div><div class="">-Nathan</div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="">
Best,<br class="">
<br class="">
John<br class="">
<div class="HOEnZb"><div class="h5"><br class="">
> On Jul 9, 2015, at 2:08 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com" class="">matthewturk@gmail.com</a>> wrote:<br class="">
><br class="">
> +1<br class="">
><br class="">
> On Thu, Jul 9, 2015 at 1:06 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" class="">brittonsmith@gmail.com</a>> wrote:<br class="">
>> This does not explicitly include the VR refactor, unless it happened to be<br class="">
>> approved in the very near future. Assuming the remaining issues with the<br class="">
>> docs build were dealt with, it would be exactly what's in dev at this<br class="">
>> moment.<br class="">
>><br class="">
>> On Thu, Jul 9, 2015 at 7:00 PM, Michael Zingale<br class="">
>> <<a href="mailto:michael.zingale@stonybrook.edu" class="">michael.zingale@stonybrook.edu</a>> wrote:<br class="">
>>><br class="">
>>> does this include the new VR interface? I'm +1 if it is the old interface<br class="">
>>> for 3.2.<br class="">
>>><br class="">
>>> On Thu, Jul 9, 2015 at 1:59 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" class="">brittonsmith@gmail.com</a>><br class="">
>>> wrote:<br class="">
>>>><br class="">
>>>> Hi everyone,<br class="">
>>>><br class="">
>>>> Nathan and I just met briefly to discuss backporting all bugfix PRs from<br class="">
>>>> the development branch to stable so as to do a minor release. This has<br class="">
>>>> become absolutely necessary as a large number of bugs have appeared and been<br class="">
>>>> fixed since the last release, which was nearly 6 months ago. By my rough<br class="">
>>>> estimate, there have been about 200 PRs accepted since the last release,<br class="">
>>>> with a large fraction of them being bug fixes. Therefore, it seemed to both<br class="">
>>>> Nathan and I that there were simply too many changesets that need to be<br class="">
>>>> picked out of dev and transplanted to stable for such an operation to be<br class="">
>>>> feasible.<br class="">
>>>><br class="">
>>>> Instead, a far simpler solution is to bite the bullet and do a 3.2<br class="">
>>>> release with everything currently in dev. Fortunately, as we require<br class="">
>>>> passing tests and documentation of new features, this would require<br class="">
>>>> relatively little effort. Most of the work is cleaning up errors in the<br class="">
>>>> docs build, for which Nathan is filing tickets as I write this.<br class="">
>>>><br class="">
>>>> I want to be clear that we desperately need a new release with the number<br class="">
>>>> of bugs that have been fixed since the last one. If we do not do this, then<br class="">
>>>> someone else needs to step up and backport all those bugfixes to stable.<br class="">
>>>><br class="">
>>>> For now, can I please get a +-1 on whether you agree with this proposal.<br class="">
>>>> If this meets with approval, then I will coordinate taking the next steps.<br class="">
>>>><br class="">
>>>> Britton<br class="">
>>>><br class="">
>>>> _______________________________________________<br class="">
>>>> yt-dev mailing list<br class="">
>>>> <a href="mailto:yt-dev@lists.spacepope.org" class="">yt-dev@lists.spacepope.org</a><br class="">
>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank" class="">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br class="">
>>>><br class="">
>>><br class="">
>>><br class="">
>>><br class="">
>>> --<br class="">
>>> Michael Zingale<br class="">
>>> Associate Professor<br class="">
>>><br class="">
>>> Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY<br class="">
>>> 11794-3800<br class="">
>>> phone: <a href="tel:631-632-8225" value="+16316328225" class="">631-632-8225</a><br class="">
>>> e-mail: <a href="mailto:Michael.Zingale@stonybrook.edu" class="">Michael.Zingale@stonybrook.edu</a><br class="">
>>> web: <a href="http://www.astro.sunysb.edu/mzingale" rel="noreferrer" target="_blank" class="">http://www.astro.sunysb.edu/mzingale</a><br class="">
>>> github: <a href="http://github.com/zingale" rel="noreferrer" target="_blank" class="">http://github.com/zingale</a><br class="">
>>><br class="">
>>><br class="">
>>> _______________________________________________<br class="">
>>> yt-dev mailing list<br class="">
>>> <a href="mailto:yt-dev@lists.spacepope.org" class="">yt-dev@lists.spacepope.org</a><br class="">
>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank" class="">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br class="">
>>><br class="">
>><br class="">
>><br class="">
>> _______________________________________________<br class="">
>> yt-dev mailing list<br class="">
>> <a href="mailto:yt-dev@lists.spacepope.org" class="">yt-dev@lists.spacepope.org</a><br class="">
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank" class="">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br class="">
>><br class="">
> _______________________________________________<br class="">
> yt-dev mailing list<br class="">
> <a href="mailto:yt-dev@lists.spacepope.org" class="">yt-dev@lists.spacepope.org</a><br class="">
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank" class="">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br class="">
<br class="">
_______________________________________________<br class="">
yt-dev mailing list<br class="">
<a href="mailto:yt-dev@lists.spacepope.org" class="">yt-dev@lists.spacepope.org</a><br class="">
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank" class="">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br class="">
</div></div></blockquote></div><br class=""></div></div>
_______________________________________________<br class="">yt-dev mailing list<br class=""><a href="mailto:yt-dev@lists.spacepope.org" class="">yt-dev@lists.spacepope.org</a><br class="">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org<br class=""></div></blockquote></div><br class=""></div></body></html>