pynum 2.0 compatibility seems to be down to a single change?

[nbpropylon]

--- a/py_stringmatching/similarity_measure/cython/cython_levenshtein.pyx
+++ b/py_stringmatching/similarity_measure/cython/cython_levenshtein.pyx
@@ -8,7 +8,7 @@ from numpy import int32
 from numpy cimport int32_t

 DTYPE = int
-ctypedef cnp.int_t DTYPE_t
+ctypedef cnp.int32_t DTYPE_t

 @cython.boundscheck(False)
 @cython.wraparound(False)
diff --git a/pyproject.toml b/pyproject.toml
index e3317e9..3980965 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -3,7 +3,7 @@ requires = [
     "setuptools>=64",
     "wheel",
     "Cython>=0.29",
-    "numpy>=1.7.0,<2.0"
+    "numpy>=1.7.0"
 ]
 build-backend = "setuptools.build_meta"

@@ -41,7 +41,7 @@ classifiers = [
     "Topic :: Software Development :: Libraries",
 ]
 dependencies = [
-    "numpy>=1.7.0,<2.0",
+    "numpy>=1.7.0",
 ]

[dahluwalia]

Hi, could you please further explain your issue? What problems are you facing with the py_stringmatching package as a result of numpy version being >= 1.70 and < 2.0?

[nbpropylon]

I'm using a later numpy version through another package, which prompted me to test what in py_stringmatching was excluding the use of a later numpy.

I may of course be completely wrong and there are other reasons why a later numpy should not be used, but the change above did produce a successful install, so I thought I should at least point it out.