dupe of #24755, the main reason this hasn’t been done is it’s an enormous amount of work (at a minimum, a large scale refactor of numpy’s C code from static python types to heap types).

Given that there is not sufficient interest and resources to resolve this “the right way”, how might you recommend one proceeds to be able to effectively incorporate NumPy et al. in a web serving environment based on Apache etc.?

I’m not looking for anything fancy or special, just the most sensible basic workaround. I ask because maybe this is more obvious to you and mentioning notes here could potentially help others.

A few starting thoughts / hypotheses:

• Virtual environments such as conda or docker may be possible to create and isolate from web serving environment and make callable with minimal nonsense
• In the most extreme scenario, I figured it could be possible to write some kind of a server API running outside of the /var/www/[website]/venv … (possibly in its own virtual env like conda or even on a different machine…) that can basically process NumPY computations for users running Apache WSGI web apps

“Simplicity is ultimate sophistication”, let me know if any ideas come to mind.

The standard solution is to use Gunicorn/Uvicorn just behind your Apache/nginx frontend to manage the numpy-using worker processes.

Thank you!

Finally implemented this change, happy to say "it works!".
As well, I think with Gunicorn it's faster too.
Thanks again.

Finally implemented this change, happy to say "it works!". As well, I think with Gunicorn it's faster too. Thanks again.

I'm having the same problem. How did you solve it? Thanks