Frank Sachsenheim

after taking a few superficial glances, just some open ended threads: - the `_collapse_whitespace` method implements the recommendations linked in `Document.collapse_whitespace`, iirc - i assume that these recommendations generally make...

i've been thinking that whitespace would make a good major topic for the 0.5 version. and, instead of relying on libxml specifics, we can implement serialization natively. that's to be...

the last cell in the `docs/getting_started.ipynb` also gives a great example where pretty is broken. so that demo-case could be taken as one test.

i started looking into [this](https://github.com/delb-xml/delb-py/issues/54#issuecomment-1207430557) which led me to realise that the serialization doesn't consider the `xml:space` attribute yet.

quick update: yesterday i was honest enough to meself to realize that i'm actually traumatized by the task of producing properly placed whitespace. but i still think the target is...

currently right now i'm in a manic phase (yes diggin to solve the problem got me to new experiences) and i imagine that the implementation will produce the most beautifullest...

yes.

yes, upgrading to 5.7 of the collection breaks existing configurations. playbook executions fail b/c `grafana_ini` is undefined. it would be fait to point out needed adjustments in a changelog.

note that there's at least a help to upgrade that was posted as [comment](https://github.com/grafana/grafana-ansible-collection/pull/232#issuecomment-2189984510) to the according PR.

if i understand you correctly, you're stating that using an environment manager to manage one virtual environment is the common case. i disagree.