lmeyerov

Same - django 3.1, python 3.7, latest constance

Any thoughts? More details: - py 3.7, django 3.1, daphne 3.0.1, asgref 3.2.10, constance 2.8.0 (latest), no channels - constance via postgres/redis - triggering scenario is `urls.py` calls `config.XYZ` as...

More complete workaround: ```python from asgiref.sync import sync_to_async from constance import config @sync_to_async def safe_constance_get(fld: str): return getattr(config, fld) z = safe_constance_get('Z') ```

mea culpa, not always the right fix: can get you a `` that'll need to be run This is a common use case so not sure

@aaronklaassen In particular, would appreciate a versioning label to avoid regression risks between upgrades :)

We prefer frozen published (non-repo) versions to decrease risks like someone maliciously taking it down, force-pushing something else at the version, etc...

Ah yes this would be great! I may be able to contribute some cycles here..

The core bit would be just https://pypi.org/project/nvgpu/ , so not hard -- any pointers on how to get started or what'd help push through rest of the way would be...

Thanks, I'll look into this! And yes, I'm guessing we can do something like `pip install nbresuse[gpu,prometheus,...]` and whatever the conda equiv is. Warning that it'll be... slow.. as we...

Great, yeah I was looking those, and indeed, was trying to figure out if this would make more sense as a collection of fat pointers or via a GPU readback!...