Contributors mailing list archives

Browse archives


Re: Warning: Using "numpy" library you will have weird errors in production even if you are not using it

Trobz, Nils Hamerlinck
- 30/01/2021 08:00:54
Thanks Moises for the heads up!

I faced a similar case.

A (non-OCA) module was using openpyxl,
which loads numpy when available,
which loads libopenblasp

OpenBLAS creates a number of threads equal to the number of core threads available: 56 in my case (production server),
so it quickly reached limit_memory_hard
and the process was killed (SIGSEGV)

Forcing OPENBLAS_NUM_THREADS=1 fixed the issue.


On Mon, Nov 2, 2020 at 3:12 PM Stéphane Bidoul <> wrote:
Hi Moises,

It's indeed unfortunate that you have had such issues. It's also very surprising that websocket-client attempts to import numpy :)

But I don't think blacklisting numpy is appropriate. It is very widely used outside OCA and can be useful at times in OCA too.


On Mon, Nov 2, 2020 at 9:01 AM Pedro M. Baeza (Tecnativa) <> wrote:
Thanks for the warning.

I don't use any OCA module using numpy AFAIK, but there are some out there indeed. Not sure if blacklisting is the best thing to do, as changing such modules to adapt to other things may not be easy, but developers that used it can tell.


Post to:

Post to: