Sébastien Besson
Sébastien Besson
Is there any remaining issue here or can this be closed?
Trying to review historical PRs in preparation of the next OMERO.py 5.20.0 milestone, what is the consensus here @will-moore @joshmoore. From the last comments, it looks like the new option...
I would propose we either assign a reviewer or close (and reopen when it's ready for review)
This is now conflicting with the changes to `omero obj` in https://github.com/ome/omero-py/pull/453. @will-moore @joshmoore how do you want to handle this?
Thanks @ehrenfeu, do you have by any chance the full stack trace of the original exception? For reference, https://github.com/ome/omero-py/pull/236 (released in OMERO.py 5.8.0) aimed to deal at a very similar...
@ehrenfeu ping
Should this be closed in favor of a PR against https://github.com/conda-forge/omero-py-feedstock as this is fairly specific to the Conda distribution mechanism?
Closing as there has been no activity for the last years and this is conflicting with the HEAD of `omero-py`. Feel free to reopen if/when a new version is ready...
Looking briefly at the way the API are called, either the full `xargs` set-up or maybe only the `omero.import.depth` set-up could potentially be moved under `do_import` so that it's only...
Hi @paulkorir, thanks for the feedback. To try to clarify your use case, would this happen in the case of separate `omero import` calls using the same stdout/stderr output file...