Josh Cannon

[Django ticket](https://code.djangoproject.com/ticket/30076#comment:1)

The ticket was accepted, and [a PR](https://github.com/django/django/pull/10822/) exists for it. That means this will be fixed in Django, and won't need any changes to this package 🎉

Hmm, I guess though if you wanted it to work in older Django versions you'd still need to make `choices` truthy. I suppose `choices=True` could work if you wanted something...

Rendering the human-readable choice. `Type: {{ object.get_type_display() }}`. Django also mentions it for tags like `regroup`: https://docs.djangoproject.com/en/2.1/ref/templates/builtins/#grouping-on-other-properties It's a really nice method. If you don't want to hack the choices...

Excellent! Do y'all have an idea of when you expect to release 2.4?

Just gonna toss this in the mix (160 being the offset of `gilstate_counter` in Py3.9 on 64-bit arch): ```rust let tstate: *mut u8 = unsafe {ffi::PyThreadState_GET().cast()}; unsafe {(*(tstate.add(160) as *mut...

Ah yes, a (admittedly nasty) workaround! ```rust runtime_builder.on_thread_start(|| { let _ = unsafe { ffi::PyThreadState_New(Python::with_gil(|_| ffi::PyInterpreterState_Get())) }; Python::with_gil(|py| { let _ = py.eval("__import__('debugpy').debug_this_thread()", None, None); }); }); ``` The chain...

I think the thread state objects are attached to Thread-Specific Storage (See https://github.com/python/cpython/blob/45e62a2bc1c0000e2e9b613fff6bebf2c26fcb93/Python/pystate.c#L1583) so my way of justifying this is we're just moving the creation of the thread state from...

Yeah once we eventually get to a minimum Python version of 3.9+ then I think PyO3 has given us all the tools we need. Documentation would be great. I doubt...

@kirankotari Yeah. Some background here, I