Andreas Motl

Thanks for the research. If we want to keep a lock file, we can have a look at Hatch or PDM. Also, there is another candidate by Armin Ronacher, only...

Hi again. Is GH-998 already the intended fix for your issue, @mhuber89? Did you have the chance to validate whether it works well for you? It looks like the improvement...

Most probably, Python 3.7 became unsupported without bumping to 0.8.0. That would be the easiest and most straight-forward explanation. We can't find anything in the [changelog](https://github.com/weaveworks/grafanalib/blob/main/CHANGELOG.rst#071-2024-01-12) about it, though, and...

Dear @davaffy, thanks for your quick reply. > [...] or 3.7 should be removed as supported version and you will need to upgrade. Yeah, I think it will be fine...

Hi again, on our downstream project grafana-wtf, we removed support for Python 3.7, and upgraded to grafanalib 0.7.1. Thanks! - https://github.com/panodata/grafana-wtf/pull/129 - https://github.com/panodata/grafana-wtf/pull/123 On matters of grafanalib itself, we submitted...

Hi Pawel. I am not a member of the grafanalib project, so I can't help you here. Apologies.

Hi. We are currently modernizing [grafana-import](https://github.com/grafana-toolbox/grafana-import) by @peekjef72, adding relevant features to support dashboard-as-code workflows. It also supports [grafana-dashboard](https://github.com/fzyzcjy/grafana_dashboard_python) by @fzyzcjy, thank you so much! Let us know about any...

Dear Gabriel, do you think GH-86 could be responsible for this regression? What happens if you add back that line at https://github.com/StefanScherer/windows-docker-machine/pull/86/files#r894786712? With kind regards, Andreas.

Hi there, we are not 100% sure, but we think we have been tripped by the same issue when conceiving [LorryStream](https://github.com/daq-tools/lorrystream). We have been able to work around it by...

## Grafana instant dashboards ### About 8abe55d3e05 added baseline support for producing Grafana instant dashboards, and 9c663b2f576d now improves it by using proper time bucketing within the standard SQL statement...