Martin K. Scherer

I think the best option would be to implement this in the fashion of the nbconvert Exporter class: https://github.com/jupyter/nbconvert/blob/a863787231f6e420d290acd98ef1e7af79b691e7/nbconvert/exporters/exporter.py#L48-L52

My current workaround looks like this. In order to generalize this, we would need to add a preprocessors argument to the application and pass it into the right spot. ```...

I would do it as in nbsphinx, e.g. just provide a list of classes specified by fully qualified names (importable names).

or have a look at the advanced scientific data format, also works like a charm.

I was not directly involved in this project, but here are my 50 cents to this topic. My suspicion is that within the C-extension we use the wrong (or lets...

I have a proposed fix for you problem. I'd be glad, if you can give it a try. You can install the fixing branch like this with pip: pip install...

I think this would be a great improvement of import speed. And with modern Python multi processing tools it'd be easy to achieve.

> As a user, I totally agree. Especially since the direct usage of setup.py got discouraged, it'd be an advantage, if pip could create a source archive.

Thanks for fixing this and extending the test!

> Python 3.11 removed a number of internal methods that we were using. These methods were used because the Python API is completely deficient in some areas like handling stack...