Graham Dumpleton

There can be so many reasons why you might not see things as being the same, especially if was being done on a different machine and not the same original...

How are you measuring the response times and where? Do you have a monitoring system in place to capture continually metrics over time? The mod_wsgi module has inbuilt capabilities to...

It has been a while since I have used this so don't remember the specific details of what it outputs, and I can't test the code right now as don't...

That event doesn't capture some of the details I was hoping to. Can you change it to: ``` import mod_wsgi def event_handler(name, **kwargs): if name == 'request_started': print("REQUEST-STARTED", kwargs) elif...

In `REQUEST-STARTED` you will see: ``` REQUEST-STARTED { 'request_id': 'EcXJbArZQG4', 'thread_id': 1, 'daemon_connects': 1, 'daemon_restarts': 0, 'request_start': 1714423920.706833, 'queue_start': 1714423920.706965, 'daemon_start': 1714423920.707038, 'application_start': 1714423920.70718 } ``` The meaning of time...

Closing since was no further follow up.

Already answered you in https://github.com/GrahamDumpleton/mod_wsgi/issues/890 Please provide in text the full Python stack trace and exception details.

👍 Due to some work changes I finally have some time now, so will be catching up on both mod_wsgi and wrapt stuff in the coming weeks.

Without any of these changes Python 3.13.0-rc.2 seems to compile and work fine under GitHub actions workflow. Was the removal of all the C APIs mentioned abandoned?

Version 5.0.1.rc1 is released on PyPi now if want to give that a try on Python 3.13.