Klaus Greff

Hi! Yes, the current solution is to create a temporary file and then add that to the database. I agree that this is a bit inelegant and it would be...

This is a consequence of the way captured functions are implemented. When an experiment is started, Sacred gathers all captured functions and initializes them with information about the current run...

Try: ```python from sacred import SETTINGS SETTINGS["DISCOVER_DEPENDENCIES"] = "sys" ``` Sacred supports four dependency gathering strategies: - `"none"`: do not gather dependencies at all - `"imported"`: collect all modules that...

That would be pretty cool, I agree. Unfortunately, it seems like PyYAML discards all comments. It seems like [ruamel](https://pypi.python.org/pypi/ruamel.yaml) might be able to handle comments, but I currently don't have...

I was thinking of setting up a virtualenv for that purpose. Maybe just by (ab)using `tox`. In principle setting up a docker image should also work. I don't have much...

That is an interesting case I hadn't thought about. So far this is not possible, no. If you are fine with only capturing stdout from within python, you could try...

@johny-c I don't think anything relevant changed. If you are still interested in this: what do you mean by some output is captured? I am asking because the capture mode...

Ohh, I found the problem: Sys-based capturing relies on replacing `sys.stdout` and `sys.stderr` with custom wrappers. But the `StreamHandler` still maintains a copy of the old `sys.stderr` and logs to...

Hi @thequilo , I know this is confusing, but it is intended behavior: named configs behave like updates, and not like normal configs (ideally I would have called them named_updates...

Yeah, capturing a function multiple times from different ingredients is not supported ATM. I hadn't thought of this usecase yet. I guess it could be implemented without too much trouble....