On 5/20/21 10:47 AM, David Mertz wrote:
On Thu, May 20, 2021 at 6:21 AM Tal Einat wrote:
I think it's worth preserving the idiom of comparing sentinels using `is`, as we do for `None` and other existing sentinel values. It's relatively easy to do, such as by using a single-value Enum or by using a class with a custom __new__.
This only works if:
a) Unpickling is within a single interpreter session
I don't understand. If I pickle a sentinel in session A, then unpickle it in session B, why wouldn't I get the "same" sentinel?
b) Sentinels are explicitly created in imported modules, not as a runtime, user-level creation
Why would you ever have a sentinel not always created?