Open glyg opened 4 years ago
- would the exluded files not appear in the output?
-f
is a local-only operation where as --exclude
requires a login so that won't do what you want.
Otherwise, :+1: for having other options like depth. Others that might make sense include:
but I'd be happy with a catch-all solution like you propose.
great (could have guessed for --exclude).
I can open a PR if you want (and can point me to the relevant tests to update / implement).
Sorry for the slow response, @glyg. When I went looking for such tests, I got lost. (i.e. they don't seem to exist)
Ha! Well it would not be bad for me as an exercise to get to know omero better to write those, would it?
Maybe I can build on https://github.com/ome/omero-py/blob/master/test/unit/clitest/test_import.py
?
:) Indeed. There are a few that have -f
options, but they aren't necessarily testing the functionality itself.
I would like to be able to pass more options to
import_candidates
, such asexclude="filepath"
if this makes sense in that context? (would the exluded files not appear in the output?)Adding a
**kwargs
agument to theas_stdout
could do the trick (or a more explicitextra_opts
):There's no rush, as I'm anticipating on problems I haven't had yet ;-)
Thanks!