There was a recent bug report with regard to ppv_cube I have a fix for, which at this point should probably go into both yt and yt_astro_analysis? Or just the latter? Sent from my iPhone

On Aug 23, 2017, at 5:18 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:

I'd like to make sure all the tests pass on Python3 before the release. I'd be happy to volunteer to fix tests that are disabled on py3.

...

On Wed, Aug 23, 2017 at 6:11 PM Britton Smith <brittonsmith@gmail.com> wrote: Hi everyone,

A while back, I brought up an ongoing effort to extract most of the yt analysis_modules into an external package called yt_astro_analysis. Here is an update on this.

The yt_astro_analysis repo is at https://github.com/yt-project/yt_astro_analysis

The documentation has been updated for all modules and includes a new front page, installation guide, and API reference. This is hosted at http://yt-astro-analysis.readthedocs.io/en/latest/

Automated testing is now enabled using Travis for most of the configurations being tested with yt's travis tests. In the process of setting this up, I noted that some of the functionality (namely, Rockstar and running halo finders in parallel) does not work on Python 3. However, this appears to be the same situation as with the versions in yt, so this is not a regression as far as I can tell.

The final things will be: 1. upload to pypi 2. perhaps update the yt install script to optionally install this 3. add deprecation warnings to the original modules in yt 4. announce a release

So, is there anything else that I missed? Are there addition things that need to happen before we can begin the final things? I would also like to invite anyone interested in this to take a look at the repo, the docs, testing, etc and offer any comments or suggestions. What does everyone think?

Thanks, Britton _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

---

yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

Great work! Thanks, Britton, for shoring up all these packages and putting this all together. I know this can be a bear of a time to do sometimes. Cameron On Wed, Aug 23, 2017 at 4:26 PM, Britton Smith <brittonsmith@gmail.com> wrote:

It's probably ok to do both for now. It's been easy to import the changes to yt_astro_analysis using git cherry pick.

On Wed, Aug 23, 2017 at 4:21 PM, John ZuHone <jzuhone@gmail.com> wrote:

...

There was a recent bug report with regard to ppv_cube I have a fix for, which at this point should probably go into both yt and yt_astro_analysis? Or just the latter?

Sent from my iPhone

On Aug 23, 2017, at 5:18 PM, Nathan Goldbaum <nathan12343@gmail.com> wrote:

I'd like to make sure all the tests pass on Python3 before the release. I'd be happy to volunteer to fix tests that are disabled on py3.

On Wed, Aug 23, 2017 at 6:11 PM Britton Smith <brittonsmith@gmail.com> wrote:

...

Hi everyone,

A while back, I brought up an ongoing effort to extract most of the yt analysis_modules into an external package called yt_astro_analysis. Here is an update on this.

The yt_astro_analysis repo is at https://github.com/yt-project/yt_astro_analysis

The documentation has been updated for all modules and includes a new front page, installation guide, and API reference. This is hosted at http://yt-astro-analysis.readthedocs.io/en/latest/

Automated testing is now enabled using Travis for most of the configurations being tested with yt's travis tests. In the process of setting this up, I noted that some of the functionality (namely, Rockstar and running halo finders in parallel) does not work on Python 3. However, this appears to be the same situation as with the versions in yt, so this is not a regression as far as I can tell.

The final things will be: 1. upload to pypi 2. perhaps update the yt install script to optionally install this 3. add deprecation warnings to the original modules in yt 4. announce a release

So, is there anything else that I missed? Are there addition things that need to happen before we can begin the final things? I would also like to invite anyone interested in this to take a look at the repo, the docs, testing, etc and offer any comments or suggestions. What does everyone think?

Thanks, Britton _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

-- Cameron Hummels NSF Postdoctoral Fellow Department of Astronomy California Institute of Technology http://chummels.org