Lev Chelyadinov

I see, thanks for the reference. I've noticed that a similar PR (https://github.com/mui/material-ui/pull/27719) has been opened for Material-UI, a very popular component library. They have put this PR on hold...

Alternatively, we could implement this behavior with a separate prop, something like `accessiblyDisabled`

Hey, thanks for the kind words. There is a way to add a component to the table, actually. Look into the named slots on the table. They receive slot props...

I didn't exactly understand what prevented you from accomplishing your goal. Would you like to elaborate on why your implementation didn't work out with the Table component as it is...

This is currently a work-in-progress PR (forgot to mark it as one, and now I can't seem to find the button).

By the way, the checks are failing because `pytest` tests are being run with `iptest`, therefore, the fixtures don't work.

Alright, we pushed our tests, now we could use some help with setting up the CI properly. Also I think the `pytest` tests are currently not being included in coverage.

There's one test that is failing for reasons unknown to us. It is `IPython.core.tests.test_magics.test_history.TestRerun.test_no_args`

Something doesn't seem right here

I think that we shouldn't have `processes` in that scheme. It's pretty vague and since we don't have any examples in our gallery that use processes, I imagine it would...