Graham Markall

Intel OpenMP disables nested parallelism by default, so it turns out we can't just remove the call entirely: https://www.intel.com/content/www/us/en/develop/documentation/oneapi-dpcpp-cpp-compiler-dev-guide-and-reference/top/optimization-and-programming-guide/openmp-support/openmp-library-support/openmp-run-time-library-routines.html.

@seanlaw You're right, it is a warning only. I looked in the past at fixing this by only using the non-deprecated API on newer OpenMPs and using the old one...

Ah, I found the PR I tried: https://github.com/numba/numba/pull/7511

> @gmarkall So, this is coming up frequently with many of our STUMPY users who are new to Python and who may not realize that it is nothing to be...

> Thank you for your input. In addition to the OpenMP warning, users are also getting [this TBB warning](https://github.com/TDAmeritrade/stumpy/discussions/507) so, in order to avoid both warnings, does that mean that...

> Ohh, does this mean that this warning is coming from the CPP layer and therefore we can't catch/filter it in the Python layer? At the end of the day,...

> @gmarkall I suggest we go with patching up the OMP backend to use the OpenMP 3 or later API and seeing what (if anything) breaks on the farm. OK,...

I wonder if the root cause of https://github.com/numba/numba/issues/8036 is a similar problem.

Thanks for the pointer - turns out that doing that alone doesn't resolve #8036. Maybe there's something else going wrong too, but it feel like that's a step in the...

Thanks for the PR! We'll look at assigning a reviewer during the next triage meeting (triage meetings occur weekly on Tuesdays)