Hi all,
I wanted to lay out a few things that I'm hoping to work on in the near term future. These are all maintenance goals for yt, not new functionality; I'm thinking that for me at least new functionality may need to take a backseat for a little while, even though it's tons of fun.
- Performance: there have been performance regressions for patch AMR code, as well as the codebase as a whole, in support of generality. I've started looking at this and hope to spend more time on it. Sam, Kacper and I have all expressed interest in plugging at this. Next week i'm going to try to set up a hangout where we look at issues, set up regression testing for performance, and then even perhaps try to address them in the hangout.
- Python3: I have spent a little bit of time working on Python 3 in the past (mostly in collaboration with Jill), and even just updated the PR this morning. There are still test failures and errors which I would like to fix. My plan here is to first get a working 2to3 codebase, and then evaluate single codebase. We've recently gotten requests for this as well.
- Infrastructure: shoring up the infrastructure to expand testing and development is a near-term goal, and Kacper and I will probably be partnering on this.
-Matt
Hi Matt, I'd be happy to help test out the python3 stuff when you think it is ready for testing.
On Wed, Jan 14, 2015 at 7:48 AM, Matthew Turk matthewturk@gmail.com wrote:
Hi all,
I wanted to lay out a few things that I'm hoping to work on in the near term future. These are all maintenance goals for yt, not new functionality; I'm thinking that for me at least new functionality may need to take a backseat for a little while, even though it's tons of fun.
- Performance: there have been performance regressions for patch AMR code, as well as the codebase as a whole, in support of generality. I've started looking at this and hope to spend more time on it. Sam, Kacper and I have all expressed interest in plugging at this. Next week i'm going to try to set up a hangout where we look at issues, set up regression testing for performance, and then even perhaps try to address them in the hangout.
- Python3: I have spent a little bit of time working on Python 3 in the past (mostly in collaboration with Jill), and even just updated the PR this morning. There are still test failures and errors which I would like to fix. My plan here is to first get a working 2to3 codebase, and then evaluate single codebase. We've recently gotten requests for this as well.
- Infrastructure: shoring up the infrastructure to expand testing and development is a near-term goal, and Kacper and I will probably be partnering on this.
-Matt
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
Hi Mike,
Thank you! As of this evening, Jill, Kacper and I have a pull request that claims to pass all the tests for 2.7 and 3.4. If you could have a shot at that (bookmark "python3" in my repo) that would be very helpful!
After doing all of this, I'm thinking we should aim for a unified codebase for 2/3 in the near future.
-Matt
On Thu, Jan 15, 2015 at 9:45 AM, Michael Zingale michael.zingale@stonybrook.edu wrote:
Hi Matt, I'd be happy to help test out the python3 stuff when you think it is ready for testing.
On Wed, Jan 14, 2015 at 7:48 AM, Matthew Turk matthewturk@gmail.com wrote:
Hi all,
I wanted to lay out a few things that I'm hoping to work on in the near term future. These are all maintenance goals for yt, not new functionality; I'm thinking that for me at least new functionality may need to take a backseat for a little while, even though it's tons of fun.
- Performance: there have been performance regressions for patch AMR code, as well as the codebase as a whole, in support of generality. I've started looking at this and hope to spend more time on it. Sam, Kacper and I have all expressed interest in plugging at this. Next week i'm going to try to set up a hangout where we look at issues, set up regression testing for performance, and then even perhaps try to address them in the hangout.
- Python3: I have spent a little bit of time working on Python 3 in the past (mostly in collaboration with Jill), and even just updated the PR this morning. There are still test failures and errors which I would like to fix. My plan here is to first get a working 2to3 codebase, and then evaluate single codebase. We've recently gotten requests for this as well.
- Infrastructure: shoring up the infrastructure to expand testing and development is a near-term goal, and Kacper and I will probably be partnering on this.
-Matt
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
trying this now (in between trips).
just to be clear, I cloned your yt repo, did 'hg update python3' and I'm going to try building it with python3 as:
python3 setup.py develop --user
and see how things go with a python3 stack.
On Fri, Jan 16, 2015 at 8:05 PM, Matthew Turk matthewturk@gmail.com wrote:
Hi Mike,
Thank you! As of this evening, Jill, Kacper and I have a pull request that claims to pass all the tests for 2.7 and 3.4. If you could have a shot at that (bookmark "python3" in my repo) that would be very helpful!
After doing all of this, I'm thinking we should aim for a unified codebase for 2/3 in the near future.
-Matt
On Thu, Jan 15, 2015 at 9:45 AM, Michael Zingale michael.zingale@stonybrook.edu wrote:
Hi Matt, I'd be happy to help test out the python3 stuff when you think it is ready for testing.
On Wed, Jan 14, 2015 at 7:48 AM, Matthew Turk matthewturk@gmail.com wrote:
Hi all,
I wanted to lay out a few things that I'm hoping to work on in the near term future. These are all maintenance goals for yt, not new functionality; I'm thinking that for me at least new functionality may need to take a backseat for a little while, even though it's tons of fun.
- Performance: there have been performance regressions for patch AMR code, as well as the codebase as a whole, in support of generality. I've started looking at this and hope to spend more time on it. Sam, Kacper and I have all expressed interest in plugging at this. Next week i'm going to try to set up a hangout where we look at issues, set up regression testing for performance, and then even perhaps try to address them in the hangout.
- Python3: I have spent a little bit of time working on Python 3 in the past (mostly in collaboration with Jill), and even just updated the PR this morning. There are still test failures and errors which I would like to fix. My plan here is to first get a working 2to3 codebase, and then evaluate single codebase. We've recently gotten requests for this as well.
- Infrastructure: shoring up the infrastructure to expand testing and development is a near-term goal, and Kacper and I will probably be partnering on this.
-Matt
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
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
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Mike,
I think this might fail because we need to run 2to3. I'd liek to get to single codebase, but not quite there yet!
On Sun, Jan 18, 2015 at 5:43 PM, Michael Zingale michael.zingale@stonybrook.edu wrote:
trying this now (in between trips).
just to be clear, I cloned your yt repo, did 'hg update python3' and I'm going to try building it with python3 as:
python3 setup.py develop --user
and see how things go with a python3 stack.
On Fri, Jan 16, 2015 at 8:05 PM, Matthew Turk matthewturk@gmail.com wrote:
Hi Mike,
Thank you! As of this evening, Jill, Kacper and I have a pull request that claims to pass all the tests for 2.7 and 3.4. If you could have a shot at that (bookmark "python3" in my repo) that would be very helpful!
After doing all of this, I'm thinking we should aim for a unified codebase for 2/3 in the near future.
-Matt
On Thu, Jan 15, 2015 at 9:45 AM, Michael Zingale michael.zingale@stonybrook.edu wrote:
Hi Matt, I'd be happy to help test out the python3 stuff when you think it is ready for testing.
On Wed, Jan 14, 2015 at 7:48 AM, Matthew Turk matthewturk@gmail.com wrote:
Hi all,
I wanted to lay out a few things that I'm hoping to work on in the near term future. These are all maintenance goals for yt, not new functionality; I'm thinking that for me at least new functionality may need to take a backseat for a little while, even though it's tons of fun.
- Performance: there have been performance regressions for patch AMR code, as well as the codebase as a whole, in support of generality. I've started looking at this and hope to spend more time on it. Sam, Kacper and I have all expressed interest in plugging at this. Next week i'm going to try to set up a hangout where we look at issues, set up regression testing for performance, and then even perhaps try to address them in the hangout.
- Python3: I have spent a little bit of time working on Python 3 in the past (mostly in collaboration with Jill), and even just updated the PR this morning. There are still test failures and errors which I would like to fix. My plan here is to first get a working 2to3 codebase, and then evaluate single codebase. We've recently gotten requests for this as well.
- Infrastructure: shoring up the infrastructure to expand testing and development is a near-term goal, and Kacper and I will probably be partnering on this.
-Matt
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
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
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
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
ok, I confirmed that it works as expected with these changes under python2.
I cannot import in python3. I can work on that if you want this evening (visiting Berkeley this week, so time is tight).
On Mon, Jan 19, 2015 at 7:46 PM, Matthew Turk matthewturk@gmail.com wrote:
Hi Mike,
I think this might fail because we need to run 2to3. I'd liek to get to single codebase, but not quite there yet!
On Sun, Jan 18, 2015 at 5:43 PM, Michael Zingale michael.zingale@stonybrook.edu wrote:
trying this now (in between trips).
just to be clear, I cloned your yt repo, did 'hg update python3' and I'm going to try building it with python3 as:
python3 setup.py develop --user
and see how things go with a python3 stack.
On Fri, Jan 16, 2015 at 8:05 PM, Matthew Turk matthewturk@gmail.com wrote:
Hi Mike,
Thank you! As of this evening, Jill, Kacper and I have a pull request that claims to pass all the tests for 2.7 and 3.4. If you could have a shot at that (bookmark "python3" in my repo) that would be very helpful!
After doing all of this, I'm thinking we should aim for a unified codebase for 2/3 in the near future.
-Matt
On Thu, Jan 15, 2015 at 9:45 AM, Michael Zingale michael.zingale@stonybrook.edu wrote:
Hi Matt, I'd be happy to help test out the python3 stuff when you think it is ready for testing.
On Wed, Jan 14, 2015 at 7:48 AM, Matthew Turk matthewturk@gmail.com wrote:
Hi all,
I wanted to lay out a few things that I'm hoping to work on in the near term future. These are all maintenance goals for yt, not new functionality; I'm thinking that for me at least new functionality may need to take a backseat for a little while, even though it's tons of fun.
- Performance: there have been performance regressions for patch AMR code, as well as the codebase as a whole, in support of generality. I've started looking at this and hope to spend more time on it. Sam, Kacper and I have all expressed interest in plugging at this. Next week i'm going to try to set up a hangout where we look at issues, set up regression testing for performance, and then even perhaps try to address them in the hangout.
- Python3: I have spent a little bit of time working on Python 3 in the past (mostly in collaboration with Jill), and even just updated the PR this morning. There are still test failures and errors which I would like to fix. My plan here is to first get a working 2to3 codebase, and then evaluate single codebase. We've recently gotten requests for this as well.
- Infrastructure: shoring up the infrastructure to expand testing and development is a near-term goal, and Kacper and I will probably be partnering on this.
-Matt
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
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
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
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
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-
Matthew Turk -
Michael Zingale