Tristan Kuehn
Tristan Kuehn
I'm in favour of the former approach I think, I can't imagine off the top of my head a lot of situations in which you'd want a warning in the...
Given that there's a straightforward workaround, we'll leave this out of 1.0 while we decide on the implementation.
Waiting on #284, will assign once that is done
The first point will be pretty easy to implement with `MultiSelectDict`
Signature proposal: `Dataset.missing_entities() -> dict[str, dict[str, list[str]]` - Components with no missing entities should be present in the dictionary, with every entity in its dictionary having the value of any...
I'm of two minds on this proposal. It seems a little beyond the scope of what Snakebids is supposed to do (i.e. I think this kind of use of provenance...
> would that code be rerun every single time snakebids or a submodule thereof is imported? If so, is that a problem? The key thing here I think is that...
> in the absence of any special actions, snakebids needs to be able to print out its logs. For anything less severe than warning, this means adding a handler somewhere....
> > Ah I guess my thinking here was that our desired default behaviour is just to print warnings, errors, and any non-log output via print (and then invoke snakemake...