Pierre Augier
Pierre Augier
@eli-schwartz I'm finally trying 1.6.0.rc1 and ~~it seems that there is a problem~~. I'm trying to understand.
It was my mistake. Just for the record, a "simple" way to check: ``` conda create -n env-mpich mpich cxx-compiler python=3.12 -y conda activate env-mpich conda install mpi4py fftw=*=mpi* fluidfft...
We can install the different implementations with conda. ```shell conda create -n env-openmpi openmpi c-compiler conda create -n env-impi impi-devel c-compiler conda create -n env-mpich mpich c-compiler ``` On Unix,...
Getting the version is not so simple: Only for OpenMPI ```sh $ mpicc --showme:version mpicc: Open MPI 5.0.5 (Language: C) ``` For other implementation: ```sh mpicc -v mpicc for MPICH...
Could a new version be uploaded to PyPI ? I'm working on [Formattex](https://foss.heptapod.net/fluiddyn/formattex), which uses TexSoup. Unfortunately, the CI is failing with TexSoup 0.3.1. Having a new version on PyPI...
Is there anyone here ?
I had no other solution than creating an alternative project on PyPI (https://pypi.org/project/texsoup-alt/). Formattex is going to use it now.
Note that `mpi4py
I confirm that `export CFLAGS=-O2` helps a lot (much faster compilation with much smaller memory consumption). However, it is not a very practical solution when using something else than pip,...
For the record, for a project using PDM, I use this workaround: ```sh export CFLAGS=-O2 # this only installs (and potentially builds) mpi4py pdm sync -G mpi --prod --no-default unset...