Hi team
Yt 4.0.0 was released on July the 6th of last year, and there’s been a bunch of contributions since then.
I would like to propose that we try to cut a 4.1 release before the summer break, roughly a year after 4.0
I think it’s both a reasonable goal and a good time for an important release. I anticipate no one will have time for coordinated work during summer, and the fall is traditionally not ideal either: many of us are on teaching duty, and it’s also when the Python ecosystem is least stable.
There are a couple blockers that need to be adressed to get the dev branch back to a release-ready state, namely
1) in 4.0 we promised (in the form of deprecation warnings) that in 4.1, errors would be raised from ambiguous name-only field keys. Actually implementing this poses a couple difficulties (see https://github.com/yt-project/yt/issues/3381 and https://github.com/yt-project/yt/issues/3839) but nothing insurmountable.
2) We need to reach a consensus on how the new axis flipping/swapping machinery should behave. There’s an open discussion for this here https://github.com/yt-project/yt/issues/3890
To get a broader (possibly more confusing) view of the TODO list, see the open milestone: https://github.com/yt-project/yt/milestone/17
I’ve highlighted what I think are the most crucial points with the “release critical” label.
You can help by discussing and triaging open issues and PRs to and from the milestone.
It’s also a good time to get feature PRs to the finish line.
We haven’t made any big “promises” for yt 4.2 (or nothing as significant as the ambiguous field stuff), so I’m hopeful that getting 4.1 out the door will allow us to make more frequent feature releases in the foreseeable future.
Any feedback is most welcome
Best
Clément
yt 4.0.4 is out !
This is a bugfix release. Most notably it fixes (future) compatibility with matplotlib 3.6, as well as a couple minor bugs.
It is available on PyPI and conda-forge. See the release notes for how to upgrade https://github.com/yt-project/yt/releases/tag/yt-4.0.4
Happy data crunching
Clément
Hi yt-dev!
I just got through reviewing @neutrinoceros's work on refactoring how norms
and colorbars are handled: https://github.com/yt-project/yt/pull/3849
A lot of effort went into it and it'd be great to get merged before it goes
stale. Anyone want to give it a look? Even if you don't have the bandwidth
to dig in too deeply, just checking out the branch and making some plots
using the new functionality would be useful and appreciated!
If I don't hear any responses (and if there are no objections), I'm
planning to go ahead and merge it next ~Tuesday -- if you **do** want to
review the PR but won't have time before then, send me a note and I'll hold
off and give more time for review.
Best,
Chris
Hi team !
Ronan Hix has successfully developed a new frontend for CHIMERA over the course of several months. A substantial amont of work went into it and it’s a very impressive first contribution.
It’s also a significant undertaking to review, but it’d be really nice to get eyes on it so we can get it in.
Here’s the pull request https://github.com/yt-project/yt/pull/3638
Any help would be appreciated, feel free to also submit partial reviews if you’d like to
Take care
Clément
