-
Notifications
You must be signed in to change notification settings - Fork 32
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
Remove metadata classes extracted to omero-metadata library #23
Conversation
I guess the same applies to https://github.com/ome/omero-upload ? Any others? |
I'd think so. Note: there's no requirement that a file under |
What's the advantage of renaming instead of removing? If |
For me, that's one of the main differences between phase 1 and phase 2: if we are releasing a phase 1 version then we shouldn't delete (yet). |
Conflicting PR. Removed from build OMERO-python-superbuild-push#70. See the console output for more details.
|
Conflicting PR. Removed from build OMERO-python-superbuild-push#71. See the console output for more details.
|
Conflicting PR. Removed from build OMERO-python-superbuild-push#72. See the console output for more details.
|
Since the first python 3 PR is merged how about rebase and merge this? |
Discussed during the python3 call today. General thumbs up to the delete strategy with the caveats that (1) the next OMERO release may not come from master of this repository and (2) that if the tests are removed here, no other repository is currently performing a merge-merge build for testing purposes. |
Closing in favor of #124 which does not drop any deprecated class and investigate a more generic strategy for handling gracefully the decoupling of CLI plugins. |
Fixes #22
The metadata library has been extracted to https://github.com/ome/omero-metadata during the OMERO 5.4.x line and the relevant classes deprecated in OMERO.py.
Originally, these classes were kept deprecated until they could be safely dropped in the next major release. With the extraction of this repository and the packaging, this is not really a safe option anymore as shown by the issue since both
omero-py
andomero-metadata
will conflict to installomero/plugins/metadata.py
.--exclude