Thilo von Neumann

As long as you don't run the script with the `--force` / `-f` flag, sacred raises an error if you pass unknown (not set in a default or named config...

This looks like a bug. Thanks for reporting! I got down to: ```python from sacred import Experiment ex = Experiment('test') ex.add_config({}) ex.add_config({}) @ex.automain def main(): pass ``` ``` $ python...

I found the issue but I don't have a good solution for this yet. It is caused by the code around here: https://github.com/IDSIA/sacred/blob/89d8bb1d71b1732bf9735752524db71af9fe349c/sacred/config/utils.py#L109-L112. The return value of the config scope...

Hi @vnmabus! Making the `Experiment` pickleable has been on my to-do list for a long time, and I would love to see this feature implemented! This is related to #441,...

Strange, the link you just posted doesn't work for me either. Are you sure your browser didn't cache it?

You are right, I was able to access the webpage outside of the University network. The problem is by far not only the `cli_option` decorator, but any decorator defined in...

That dependency was added before I started to work with sacred, so I don't know exactly why it was added, but it has a few nice properties and claims to...

Not exactly, ```python import functools def decorator(fn): @functools.wraps(fn) def wrapper(): return fn() return wrapper class A: @decorator def f(self): pass import inspect inspect.ismethod(A().f.__wrapped__) ``` gives `False`. To detect if `f`...

No, it only uses the `wrapt.decorator` functionality. And I'm not even sure if the information on whether a captured function is bound is necessary for these decorators. So we may...

I tried to remove `wrapt` from the `captured_function` and make it pickleable. Removing `wrapt` was quite easy and the code looks (in my opinion) even cleaner. There is just one...