Eric G. Kratz
Eric G. Kratz
@arjxn-py Can we close this now?
I thought the consensus was that it was not a major bottleneck so the work/code required to do it was bigger than the problem
We can always open new tickets when problems recur, no need to keep this open
Can you add some tests for this?
@Saswatsusmoy Are you still working on this?
Docs look correct now, but the example notebooks are failing. This passed right before this, so I am going to try just retriggering it
I don't think I have seen it recently either
@santacodes Just an FYI, force pushing removes the history of what was reviewed. Try not to force push after review has started
Not sure if it deserves to be its own focus area, but I am planning on focusing on the following infrastructure topics for this year: - [ ] Python 3.13...
@prady0t Can you summarize what is not covered in #3617 so that we can close the older issue?