Stefan Scherfke

The possible to use a local source for mermaid is document but does not work. This JS snippet also won't work with a local JS file: https://github.com/mgaitan/sphinxcontrib-mermaid/blob/master/sphinxcontrib/mermaid/__init__.py#L45-L48 It would be...

I think that 0c02f29fa259c3173ed0c0b6247a093f41ac312f _really_ fixes the problem in the right way. I added a longer description to the commit to explain why. Let me know, what you think :)

@hynek could you please re-open this MR? I think we misunderstood each other. The issue is still relevant and the MR went in the right direction. I will finish it...

This is an expected change. `repr()` is now used for _every_ object, including strings. This is needed so that [Pydantic Secret Types](https://docs.pydantic.dev/2.1/usage/types/secrets/) and [Typed Settings SecretStr](https://typed-settings.readthedocs.io/en/stable/apiref.html#typed_settings.types.SecretStr) do not leak. For...

Okay, Pydantic is not affected – their `Secretstr` does not inherit `str`. Either they changed behavior in v2 or I didn't remember it correctly.

Rich's "to_repr" implementation does the same thing and when printing `"'spam'"` it becomes just `'spam'` which is the (new) expected result. So imho, this issue should be closed as wontfix/works-as-expected/......

The dict of locals which is part of the stacktrace is now a dict mapping names (as strings) to reprs (as strings). In the older versions, there was an exceptions...

The `to_repr()` function is only used by the dict tracebacks and that is only (usually) only used with a JSON renderer. And then only the looks of strings are changed...

@hynek I think this can be closed as *stale*.

I don't think I introduced this in the last release and I think that @raqbit is right in admitting that is was wrong to call `exception()` outside an exception handler....