Catch signal error in dynesty

This was preventing dynesty from running on Windows systems because these signal attributes don't exist on Windows systems.

changed milestone to %0.6.6

added Bug label

Does this mean that checkpoints won't be written on keyboard interrupts? Is this an issue? Is there any way to catch these signals on windows.

Before merging this, I'd like to see it verified that this has no impact on running on an LDG cluster. While on the face of it I can't see any reason it should, if it does it effects a lot of people.

I can have a look into that.

mentioned in merge request !755 (merged)

changed milestone to %0.6.7

changed milestone to %0.6.8

resolved all threads

added 53 commits

• 1ef62581...0140d1e7 - 51 commits from branch master
• fdc17676 - Merge remote-tracking branch 'origin/master' into catch_signal_error_dynesty
• 8ca3af9c - Changed the log-level of the signal attribute check to be debug

Compare with previous version

added 1 commit

• c1a8e9e0 - Fixed formatting

Compare with previous version

approved this merge request

unapproved this merge request

approved this merge request

approved this merge request

merged

mentioned in commit 19d44d79