windows

[videlec]

Because windows does not support POSIX signals, the current cysignals does not work on this platform. However, windows handles the floating-point exception (SIGFPE) similarly to POSIX signals. Using this fact, cypari provides a fork of cysignals that works on windows. See the explanation at line 372 in implementation.c. This special handling for windows only concerns windows and the code remains unchanged for other platforms.

A windows port would benefit to several Python libraries that want support for windows (e.g. giacpy, cypari2).

[johnyf]

As a sidenote, it appears that cysignals works using Cygwin:

cysignals/setup.py

Lines 34 to 37 in acc2ba9

	if sys.platform == 'cygwin':
	# On Cygwin FD_SETSIZE defaults to a rather low 64; we set it higher
	# for use with PSelecter
	# See https://github.com/sagemath/cysignals/pull/57

[jdemeyer]

As a sidenote, it appears that cysignals works using Cygwin:

Yes, it does.

[vinklein]

Hi,
I am currently working on this subject and have a first compiling prototype/draft (windows_dev).

I am currently looking to translate tests.pyx for windows, it's uneasy because of the lack of proper fork and kill (Send signal manually) equivalents in windows.

Edit: As i have found an answer to my question i just keep this post for informational purpose.

[vinklein]

Here is a first step-by-step guide to install cysignals on windows in case of someone want to test the current windows_dev.

[jdemeyer]

Hello Vincent. It's not clear to me if you expect some feedback at this time.

If you are serious in porting cysignals to Windows, you really need to set up continuous integration (on Windows, this is typically done by Appveyor).

[vinklein]

Hello Jeroen. Yes feedback is welcome at this point.

If you are serious in porting cysignals to Windows, you really need to set up continuous integration (on Windows, this is typically done by Appveyor).

I will look at it. Thanks.