Sorry about that. It is pip installable of course. However, it uses some non standard setup.
I've been too long out of the topic. I just noticed that there is no active development. This might be fine. But I'm not sure. On Sun, Apr 30, 2023, 19:27 Matthias Koeppe <matthiaskoe...@gmail.com> wrote: > I would suggest looping in the Cython community (cython-users list) on > these questions. > > Could you elaborate on "cysignals is not pip-installable"? We are even > building platform wheels - https://pypi.org/project/cysignals/#files > > On Sunday, April 30, 2023 at 7:49:44 AM UTC-7 jonatha...@googlemail.com > wrote: > >> Hi, >> >> it's been over a year since the last activity on >> https://github.com/sagemath/cysignals. >> >> This could well be, because it is a good shape, but looking at the >> issues, I'm not too sure about that. Here are some issues, I know of: >> >> - sig_on/sig_off is poorly maintained and not thread safe >> - cysignals is not pip installable and highly platform dependent (and on >> a platform even depends very much on the compiler). >> - Memory: Interrupting sig_on...sig_off will not clean up the heap. >> >> I would argue: >> >> - To my knowledge, `sig_check` is pretty much equivalent to ` >> PyErr_CheckSignals` (https://github.com/sagemath/cysignals/issues/145) >> - Instead of using `sig_on...sig_off` for our own functions, we should >> check for signals at reasonable places. >> - External calls should be interrupted with standard tools and not our >> own custom tool. >> >> While the action on the first item is quite obvious (I didn't even check >> if anything needs to be done here), I have not done my research on the >> second point and what the alternatives are. >> >> Before I dig into possible options of replacing `sig_on...sig_off`, I >> would like to gather your opinions: >> >> Does cysignals get enough support to keep going or do we want to try a >> different approach? This different approach will for sure not be as >> efficient, but will probably need less effort to maintain. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "sage-devel" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/sage-devel/MYV3wDR83m4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/dfe10ff3-aa4b-4587-8e60-4ff60769a9edn%40googlegroups.com > <https://groups.google.com/d/msgid/sage-devel/dfe10ff3-aa4b-4587-8e60-4ff60769a9edn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAOOXL%2BoUubXTJSuyzXnSLxDn9sjaAYTBJoXm7ks8Dx05%2BHPn9Q%40mail.gmail.com.
