Alexis DUBURCQ

Here is my config that working that is the closest to yours. I hope this helps ! ``` ldap_servers: ldap:// ldap_bind_dn: uid=,cn=users,cn=accounts,dc=local,dc= ldap_bind_pw: ******************* ldap_auth_method: bind ldap_search_base: cn=accounts,dc=local,dc=tplusone,dc=io ldap_group_search_base: cn=groups,cn=accounts,dc=local,dc=...

Perfect ! Yes adding more details would be beneficial to many I think. Being able to apply group filter does not sound very uncommon. FYI regarding password length, personally I'm...

I think I will try to use `numpy/_core/include/numpy/npy_2_compat.h` instead of dealing with backward compatibility manually. It sounds more reasonable.

I changed my mind. Since `npy_2_compat.h` must be vendored to get backward compatibility. The current MR with the previous one is basically the same without dedicated header.

For now, something is broken, and it is not clear to me why. I will ask on numpy repo: ```bash ImportError: /home/runner/.local/lib/python3.10/site-packages/jiminy_py/core/core.cpython-310-x86_64-linux-gnu.so: undefined symbol: EIGENPY_ARRAY_APIPyArray_RUNTIME_VERSION ``` [here](https://github.com/numpy/numpy/issues/26091) is the corresponding...

After a long discussion with numpy team, it turns out that numpy API should not be exposed the way it is to avoid compatibility issues. Actually every import of numpy...

@jcarpent No. Here is the current state of the discussion https://github.com/numpy/numpy/issues/26091. A feedback from Eigenpy team was requested to decide in which direction to go next, since different options are...

Apparently, changes were merged into Numpy recently https://github.com/numpy/numpy/pull/26103. It is now possible to expose Numpy symbols in release 2.0 as it used to be previously. I will have a look...

@seberg Thank you for the clarification. Indeed I made the assumption of backport in Numpy 2.0 since this release was still in a release candidate and not definitive, but it...

Exactly, @seberg summed it up pretty well.