Graham Dumpleton

Closing this issue at this point. Should get out a new released version of mod_wsgi in coming week after see if anything else need to roll into a new release.

Yes, your understanding is correct and does look like it needs to be fixed. Thanks for noticing.

Closing as change was added to develop branch and hope to have new release in coming week.

Is this just meant to be for the benefit of others, or are you expecting help on something? Post is a bit confusing.

Because you posted what is the normal solution, which is to install the `python3-devel` package. What is in the `/usr/include/python3.11` directory on your system after having installed that package?

According to RHEL docs: * https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/installing-and-using-dynamic-programming-languages_configuring-basic-system-settings#con_python-versions_assembly_introduction-to-python you possibly should be trying to install `python3.11-devel` and not `python3-devel`.

What ever Python package you are using is expecting to only ever be run in a process context where stdout/stderr are linked to a tty device or file. Python doesn't...

I still need to see the full Python stack trace from the Apache error log to understand what is the calling sequence.

The problem is here: * https://github.com/microsoft/playwright-python/blob/c6cc4c97cc9e1bccd66c7f2a54bc44b627903f24/playwright/_impl/_transport.py#L39 That package takes code from faulthandler which back in time was known not to handle very well when stdout/stderr were not associated with a...

I have no idea what playwright is for. I am presuming where it is failing is nothing to do with logging as such. There wouldn't be any point in changing...