-
Notifications
You must be signed in to change notification settings - Fork 41
Conversation
God damnit I don't want to have to fix sphinx and conda build issues just to archive this repo anyway. @keewis do you think I can just merge and release this regardless of the CI not working? |
we have to fix |
This is interesting - this change was done by Stephan recently as part of the datatree refactor. I think I will just pin xarray to <=2024.09.0 (the last released version before that change). If that causes a problem for anyone then it's just a sign they should migrate. |
I think pinning should be fine, nobody should need to have two versions of If it's fine with you I'll try to get the docs to at least compile (by pushing to this branch). |
looks like the issue was the deprecation / discontinuation of Edit: it passed on RTD, not just locally |
I think we can ignore the failing dev CI ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually, one comment about the links to the migration guide, but otherwise this looks good to me
datatree/__init__.py
Outdated
warnings.warn( | ||
"The repository `xarray-contrib/datatree` has been archived! It is no longer maintained as of October 2024. " | ||
"Datatree functionality has been migrated upstream to `pydata/xarray`, so please use `xarray.DataTree` instead. " | ||
"To help you migrate there is a guide at https://github.com/pydata/xarray/blob/main/DATATREE_MIGRATION_GUIDE.md", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this might be tricky to change since we do plan on moving it out of the xarray
repository at some point. Should we instead point to a dedicated discussion here that we can more easily modify?
docs/source/index.rst
Outdated
|
||
There will be no further bugfixes or feature additions to this respository. | ||
|
||
Users of this repository should migrate to using `xarray.DataTree` instead, following the `Migration Guide <https://github.com/pydata/xarray/blob/main/DATATREE_MIGRATION_GUIDE.md>`_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here: should we link to a discussion on the datatree repository?
Perhaps I should raise one single issue on this repo and pin it, as another form of warning. That becomes read-only once archived though. That can have a multitude of links, and we can point to that issue from the warning. How does that sound? |
also thank you helping with that! Really appreciate it. |
That's fine, you can temporarily un-archive a repository to change the link – which is much easier than having to re-release again with a changed link. But otherwise this sounds good to me! |
Raised #345, so I will merge this PR and release as soon as we release xarray. |
after updating the links? |
By updating the links you mean link to the new release of xarray? I can do that. |
nah, I meant change the link to the migration guide to issue. Also, might be good to ask people to open discussions on the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking of something like this, but doesn't as helpful as directly linking to the guide. However, just to really stress this, I do think we can save ourselves a lot of trouble by keeping the link to the migration guide mutable.
README.md
Outdated
PLEASE RAISE NEW ISSUES ON THE XARRAY REPOSITORY UPSTREAM | ||
There will be no further bugfixes or feature additions to this respository. | ||
|
||
Users of this repository should migrate to using `xarray.DataTree` instead, following the [Migration Guide](https://github.com/pydata/xarray/blob/main/DATATREE_MIGRATION_GUIDE.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Users of this repository should migrate to using `xarray.DataTree` instead, following the [Migration Guide](https://github.com/pydata/xarray/blob/main/DATATREE_MIGRATION_GUIDE.md). | |
for more information and a link to the migration guide see [this issue](https://github.com/xarray-contrib/datatree/issues/345) |
Maybe actually instead I should make a new discussion on |
that would be better, actually, people are less likely to try to open an issue here if we directly link to the |
No description provided.