-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.10 Release #1535
Comments
Great; there's only a single action item left on #1272, so I'll try to get to that later this week. |
Can we add:
to that list? |
@fujiisoup is finishing up #1473 (vectorized indexing) but we still have one unresolved concern: existing uses of xarray objects to index other xarray objects will break in some cases, because the behavior of vectorized indexing will depend on dimension names and coordinates on indexer objects. In particular: behavior will change if the indexer object goes along a different dimension than the corresponding dimension of the indexed object (e.g., for Unfortunately, there isn't a good way to deprecate the existing behavior while introducing the new behavior, since the meaning of this type of indexing will change. We could do a deprecation cycle (#1333), but that will mean delaying this highly useful form of indexing. For what it's worth, I think this the last major breaking change of this type that we will need for xarray. (Though we might choose to do some other clean-ups before the v1.0 release) Are we OK with this breaking change for the 0.10 release? It would be accompanied by a large note under "Breaking changes" in the release notes. (Free to express your opinion with 👍 or 👎 on this comment.) |
@shoyer and @fujiisoup - are we going to take care of #1333 as part of #1473? |
Yes.
|
OK, I really want to get the release candidate (and the release) out promptly. #1663 in particular is going to be annoying for users with pandas 0.21 out. I think #1615 (unicode string in netCDF3) and #1648 ( The last outstanding PR from the top is #1489 ( |
This all sounds good to me. There is also #1485 that can go in now. We were just waiting since it has some changes to the issue template on github. |
I think we're down to the last few PRs, all of which are nearly ready to go in:
I plan to issue the RC as soon as all of these are merged. |
@shoyer - I just merged the last two PRs. We're feature complete for v0.10! |
OK, I'm going to issue the release candidate! |
The release candidate has been tagged and is on pypi. Docs are also up: |
The second release candidate seems to have been received well. @benbovy and @fujiisoup fixed two issues (#1723 and #1724), but neither of them were actually introduced by rc2. So I think it's time to issue the final release. I'll do so tomorrow unless there are any objections. |
The release is tagged and on pypi: https://pypi.python.org/pypi/xarray I'm waiting for read the docs to finish its rebuild before sending out an announcement to the mailing list. |
Great. Thanks @shoyer! |
Awesome! |
I just merged the update on conda-forge: conda-forge/xarray-feedstock#26 |
I'd like to issue the v0.10 release in within the next few weeks, after merging the following PRs:
Features
to_dask_dataframe()
(@jmunroe)pathlib.Path
support toopen_(mf)dataset
#1514 Addpathlib.Path
support toopen_(mf)dataset
(@willirath)Bug Fixes
__repr__
and__getattr__
(@crusaderky)Misc
xr.show_versions()
(@jhamman)TODO
Let me know if there's anything else critical to get in.
CC @pydata/xarray
The text was updated successfully, but these errors were encountered: