On Sun, 16 Apr 2023, Matthew Knepley wrote: > On Sun, Apr 16, 2023 at 12:34 AM Pierre Jolivet <pierre.joli...@lip6.fr> > wrote: > > > petsc4py build is not broken, but maybe it is not future-proof and can’t > > handle Cython 3.0.0b2 (or there is a regression in Cython). > > Could you downgrade your Cython (to an actual release and not a beta) and > > see if the error persists? > > > > You are correct. However, I think this is a bug in the petsc4py install > now. I had deleted my Cython, and it was fetched automatically.
Strange. I'm getting: [balay@pj01 petsc]$ python3 -m pip install --user cython Collecting cython Using cached Cython-0.29.34-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl (1.9 MB) Installing collected packages: cython Successfully installed cython-0.29.34 > I think we need to change > > src/binding/petsc4py/conf/confpetsc.py:133 > > I just changed '>=' to '==', but maybe we just put a '< 3' since it is > incompatible with the 3.0.0.b2 which setuptools > is automatically bringing down. Can you create an MR [to release]? I think Lisandro would have to check on this [I guess support both CYTHON_MIN and CYTHON_MAX] Satish > > Thanks, > > Matt > > > > Thanks, > > Pierre > > > > > On 16 Apr 2023, at 12:25 AM, Satish Balay via petsc-dev < > > petsc-dev@mcs.anl.gov> wrote: > > > > > > Works for me with latest main - so I'm not sure whats going on here.. > > > > > > Is this reproducible in a clean clone? Also - are you using mpi4py in > > this build? > > > https://gitlab.com/petsc/petsc/-/issues/1359 > > > [this issue looks different though..] > > > > > > Satish > > > > > > ------ > > > > > > *** Building petsc4py *** > > > running build > > > running build_src > > > using Cython 0.29.33 > > > cythonizing 'petsc4py/PETSc.pyx' -> 'petsc4py/PETSc.c' > > > running build_py > > > creating build > > > creating build/lib.linux-x86_64-cpython-311 > > > creating build/lib.linux-x86_64-cpython-311/petsc4py > > > copying src/petsc4py/PETSc.py -> > > build/lib.linux-x86_64-cpython-311/petsc4py > > > copying src/petsc4py/__main__.py -> > > build/lib.linux-x86_64-cpython-311/petsc4py > > > copying src/petsc4py/__init__.py -> > > build/lib.linux-x86_64-cpython-311/petsc4py > > > creating build/lib.linux-x86_64-cpython-311/petsc4py/lib > > > .... > > > > > > > > > On Sat, 15 Apr 2023, Matthew Knepley wrote: > > > > > >> I get > > >> > > >> *** Building petsc4py *** > > >> running build > > >> running build_src > > >> removing Cython 0.29.30 from sys.modules > > >> fetching build requirement 'Cython >= 0.29.32' > > >> Searching for Cython>=0.29.32 > > >> Best match: Cython 3.0.0b2 > > >> Processing Cython-3.0.0b2-py3.8-macosx-10.9-x86_64.egg > > >> > > >> Using > > >> > > /PETSc3/petsc/petsc-dev/src/binding/petsc4py/.eggs/Cython-3.0.0b2-py3.8-macosx-10.9-x86_64.egg > > >> > > >> using Cython 3.0.0b2 > > >> cythonizing 'petsc4py/PETSc.pyx' -> 'petsc4py/PETSc.c' > > >> /PETSc3/petsc/petsc-dev/src/binding/petsc4py/conf/cythonize.py: No such > > >> file or directory: 'petsc4py/PETSc.pyx' > > >> error: Cython failure: 'petsc4py/PETSc.pyx' -> 'petsc4py/PETSc.c' > > >> **************************ERROR************************************* > > >> Error building petsc4py. > > >> > > >> Thanks, > > >> > > >> Matt > > >> > > >> > > > > > > > > >