Joachim Jablon

I'll close this for now, please feel free to re-open if there's still a problem.

Oh, maybe I didn't understand your point then.

It looks like the official vault binary always writes as a string, and will try to read as complex object only when writing. The ticket says: > "vault-cli get" doesn't...

What you'd be looking for IMHO: - long-decription from README.md (https://pypi.org/project/vault-cli/ / https://github.com/peopledoc/vault-cli/blob/master/setup.cfg#L8-L9 ) - Homepage URL and project urls pointing to all the relevant places (docusign docs, this github...

Oh BTW, your toxfile is not specifying which python3 subversion it's testing so it's kind of ambiguous. It would feel better to explicitely decide what you support and what you...

Anything new on this ? #29 could be dealt with at the same time.

On [my project](https://github.com/peopledoc/procrastinate), the doc builds correctly for Sphinx 3.x and fails (because warnings treated as errors) on 4.x. I'll need to stay on 3.x until it's resolved, but if...

There's a similar but different issue causing the same messages at #10088 and an ongoing PR in #10089 . Is there a chance it solves your issue ?

Might be related or not, but https://github.com/sphinx-doc/sphinx/pull/10089 was recently merged, and maybe it's involved in the change of behaviour you observed. Let me know: if I as the one breaking...

> Unrelated as I was already using 5.1.1 It's the other way around. My question is whether or not the fix included in 5.1.1 _introduced_ the issue. Also, you may...