Bug 2336965 - python-sep: FTBFS in Fedora Rawhide: Error compiling Cython file: 'int_t' is not a type identifier
Summary: python-sep: FTBFS in Fedora Rawhide: Error compiling Cython file: 'int_t' is ...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-sep
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Sergio Pascual
QA Contact: Fedora Extras Quality Assurance
URL: https://koschei.fedoraproject.org/pac...
Whiteboard:
Depends On:
Blocks: F42FTBFS PYTHON3.14 NUMPY2
TreeView+ depends on / blocked
 
Reported: 2025-01-10 16:15 UTC by Karolina Surma
Modified: 2025-02-10 09:36 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 09:36:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Karolina Surma 2025-01-10 16:15:25 UTC
Description of problem:
Package python-sep fails to build from source in Fedora Rawhide.

Version-Release number of selected component (if applicable):
1.2.1-11.fc41

Steps to Reproduce:
koji build --scratch f42 python-sep-1.2.1-11.fc41.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/python-sep

Reproducible: Always

Actual Results:  
Multiple times:

+ /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP'
/usr/lib64/python3.13/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /builddir/build/BUILD/python-sep-1.2.1-build/sep-1.2.1/sep.pyx
  tree = Parsing.p_module(s, pxd, full_module_name)
Error compiling Cython file:
------------------------------------------------------------
...
# Source Extraction
# This needs to match the result from extract
cdef packed struct Object:
    np.float64_t thresh
    np.int_t npix
    ^
------------------------------------------------------------
sep.pyx:555:4: 'int_t' is not a type identifier


This has started to happen since update to numpy 2.


Note You need to log in before you can comment on or make changes to this bug.