Hi Sebastian,
On 15.04.20 09:45, Sebastian Ramacher wrote: > Looking at aoflagger's build system, it could be affected by the same > issues during the next Python 3 transition. The build system currently > doesn't ensure that the libpython and libboost-python versions are > compatabile. So let's keep this bug open to get this properly fixed for > the next Python 3 transition. The problem now re-appears, since boost it now 1.71 by default and this seems to not work. Pinning it to 1.67 helps. However, I think this is fragile and will break in future again. What is the right way to ensure libpython3 and libboost-python are compatible? What is the reason that they are not in the moment? Best regards Ole
