Pierre Augier

Results 181 comments of Pierre Augier

Thanks @stefanv for your notes. I worked on a merge request to improve the situation (https://foss.heptapod.net/fluiddyn/fluidimage/-/merge_requests/116) and opened two issues related to two of your remarks. > The README has...

Thanks @Kai-Striega for looking at this! PDM will never install things globally. No need to use `PDM_IGNORE_ACTIVE_VENV`. Just deactivate all virtual environment and use it. PDM is going to create...

This is still an issue. Thus, Meson is very bad for MPI. For example, if I understand correctly, packages using Meson and MPI cannot be built with mpich on conda-forge.

I guess we could follow what Pythran (https://github.com/serge-sans-paille/pythran) does. The Pythran package contains a lot of C++ files (in https://github.com/serge-sans-paille/pythran/tree/master/pythran/pythonic), which are used during compilation of C++ extensions produced by...

I had a look and it seems that Pythran does not include its own sources, which are just used as headers and then users need to use `pythran.get_include` in their...

It would be useful that Python 3.13 be supported. filetype seems nice and with an active repo but the last version was released on 2022: https://pypi.org/project/filetype/#history (see also https://github.com/h2non/filetype.py/issues/188) In...

> Is CPython prioritising extension module over .py files a guaranteed behaviour, or an implementation detail that gets exploited and relied on? I get this can be useful, but maybe...

I finally asked a question related to this issue [here](https://discuss.python.org/t/clarification-status-priority-between-extensions-and-py-files/9670).

For the editable installs Meson-python does something which could be used for HPy: - A Python file and a .pth file are added to the wheel: https://github.com/mesonbuild/meson-python/blob/041ed596e0c43ebb6076c38a0b59aa2e71e687b5/mesonpy/__init__.py#L504 - The .pth...

These texts ([manifesto](https://github.com/hpyproject/hpy/wiki/c-api-next-level-manifesto) and [What needs to change and why](https://github.com/hpyproject/hpy/wiki/c-api-next-level-changes)) are nice and we can see if the current documentation can be improved with them. But I also think that...