You may also modify:

• Lib/asyncio/unix_events.py: "if not (1 <= sig < signal.NSIG):" in _check_signal() -- don't forget to patch Lib/test/test_asyncio/test_unix_events.py
• Lib/test/support/__init__.py: SaveSignals uses "self.signals = list(range(1, signal.NSIG))"

Thanks for the comments. You're right about Windows. I'll also fix asyncio and test.support.

Big +1 for this feature. Can you make it return a frozenset though?

Frozen sets are nice if you want to hash them, otherwise I don't really see the point.

Frozen sets are nice if you want to hash them, otherwise I don't really see the point.

What's the point of being able to modify the returned set? ;) If you return a frozenset you can cache it (something that I would recommend doing in this PR anyways).

This isn't a deal breaker, it's just that I would use a frozen set here. Overall LGTM.

Other functions like signal.pthread_sigmask and signal.sigpending return plain sets. So we could return a frozenset from signal.valid_signals but that sounds a bit gratuitous. @vstinner, what do you think?

First I wanted to get a list, but then I read the PR and I like reusing existing code :-)

If someone wants an immutable type, it's very simple: frozenset(signal.valid_signals()).

An immutable type might be justified if it was a module constant, but it's a function which creates a new object at each call, so IMHO a set is just fine.

I don't want to modify other signal functions just to be pedantic. I like Antoine's rationale to use set in valid_signals().