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
Split IO #2 #2972
Split IO #2 #2972
Conversation
Considering that there is not much left to do, I would prefer to finish in the next few days. After that, I am happy to give a go at splitting! :) |
+1 - would be great if you could do so! @pietsjoh will be starting to contribute new readers in the next weeks and it would be great to do so directly to the new repo. P.S.: I am available until Tuesday to review the remaining steps. |
The remaining tasks are done in francisco-dlp#58. @francisco-dlp, just in case, we can merge and push to your branch, would have time to review and merge francisco-dlp#58? The change are mostly trivial. Worst-case scenario, we create another branch but it would be better to keep it all in this PR! |
[SPLIT-IO] last few tasks
Just realized that
I would propose merging this one nevertheless and sorting out anything related to the v1.7.1 merge into RnM in a separate PR, possibly including the changelog entry of this PR (which should actually be about the split and not about the preparation of the split). |
Yes and there is some tidying up needed on the RELEASE_next_major branch too! |
For the record, here are the step that I did to split into a separate repository: Command to split the repository
I needed to add all relevant paths to keep the history after folder renames, etc. Tidy up left over codeSince it was necessary to also filter Clean some large file from the historyWe had some large which were added and removed from code during a pull request and never cleaned up. This was possible to find them using the following command:
ref: https://stackoverflow.com/questions/10622179/how-to-find-identify-large-commits-in-git-history The largest file before history cleaning were:
And are now
I keep a local copy of the git repository before in case something was incorrect! After hyperspy 2.0 is released, we should possibly do the same to the hyperspy repository. |
Thanks Eric for finishing it up! |
Follow up of #2972 and tidy up left up rosettasciio
Description of the change
Split HyperSpy's IO plugins into a separate package RosettaSciIO. See #1978 for the related discussion.
This supersedes #2174
Progress of the PR
DictionaryTreeBrowser
. DTB was replaced by python-boxmisc.io
code torsciio
rsciio
.rsciio
Most of it is done, except for:rgb_tools
emd
relies on hyperspy for reading_hierarchical
fully independent of HyperSpyfile_writer
sfile_writer
work with dictionary francisco-dlp/hyperspy#51)file_writer
work with dictionary francisco-dlp/hyperspy#51)file_writer
work with dictionary francisco-dlp/hyperspy#51)file_writer
work with dictionary francisco-dlp/hyperspy#51)file_writer
work with dictionary francisco-dlp/hyperspy#51)file_writer
work with dictionary francisco-dlp/hyperspy#51)upcoming_changes
folder (seeupcoming_changes/README.rst
) -- see Merge RELEASE_next_minor into RELEASE_next_major #2979,readthedocs
doc build of this PR (link in github checks)How to test it
To test it, simply install
rosettasciio
(currently at hyperspy's root folder, it'll move to its own repository once there are no more code exchanges between hyperspy and RosettaSciIO) in addition to hyperspy. Everything should work as usual.Additionally, it is possible to import the readers directly from RosettaSciIO as follows: