Source: dolfin
Followup-For: Bug #1088865
I tested my own legacy code with dolfin on python3.13.
It's still running perfectly fine.
It looks like the damage here is restricted to the mesh iterators,
in MESHITERATOR_MACRO and also mesh.SubsetIterator()
If you're not using those iterators, then th
Source: dolfin
Followup-For: Bug #1088865
All of the MESHITERATOR_MACRO functions in python/src/mesh.cpp are
affected (cells, facets, faces, edges, vertices)
so I guess the problem is somewhere in MESHITERATOR_MACRO:
#define MESHITERATOR_MACRO(TYPE, NAME) \
py::class_, \
std::
Source: dolfin
Version: 2019.2.0~legacy20240219.1c52e83-11
Followup-For: Bug #1088865
The mesh itself seems to be fine.
>From Francesco's example, both python 3.12 and 3.12 give
>>> mesh.cells()
array([[0, 1, 4],
[0, 3, 4],
[1, 2, 5],
Source: dolfin
Version: 2019.2.0~legacy20240219.1c52e83-11
Followup-For: Bug #1088865
X-Debbugs-Cc: francesco.balla...@unicatt.it, po...@debian.org,
dpars...@debian.org
Hi,
I can reproduce this locally, even on a amd64 arch. Simplest file that shows
the issue is
$ cat file.py
from dolfin import
Source: dolfin
Version: 2019.2.0~legacy20240219.1c52e83-11
Severity: serious
Hi,
autopkgtests for dolfin are currently failing, blocking testing migration
and the openmpi transition. See:
https://tracker.debian.org/pkg/dolfin
https://tracker.debian.org/pkg/openmpi
Cheers,
Emilio
5 matches
Mail list logo