Thilo von Neumann

I finally got the release workflow to work (after a few deleted releases, but there was no other way to test it...) and sacred Version 0.8.4 is published on PyPI!

I'll close this issue since there will be no 0.8.3 release on PyPI

Okay, you convinced me that it's necessary to publish a new release to PyPI (and I am myself very annoyed by the fact that the latest release is basically unusable)....

@AdamGleave is not wrong, there is a risk of sacred becoming unmaintained when I step out. As I am currently a Ph.D. student, and it's completely unclear what will happen...

I observed the same issue with a note like this: ``` [[A]] # Heading ``` where `Heading` is detected as heading for the link `[[A]]`. I guess this is related...

This looks like a git error. Can you provide any more information to pinpoint the issue?

Hi @mrzv! The documentation is actually correct, that's (almost) the type annotation of `os.PathLike` (https://docs.python.org/3/library/os.html#os.PathLike). So, you can path a file path as bytes (as stated in the docs), but...

Hi! No, sacred doesn't support automatic data versioning.

Named configs are _always_ evaluated before "normal" configs, no matter where they are defined. This is the place where it happens: https://github.com/IDSIA/sacred/blob/cd90ee1f55df04e2bb55d2e3b6badcd7c2a30bfe/sacred/initialize.py#L420-L442 While I agree that this is confusing and...

And currently you can overwrite a sub-ingredient's config from its parent. Run `with named`: ```python from sacred import Experiment, Ingredient i = Ingredient('i') @i.config def defaults(): a = 42 ex...