Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6071761
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T10:05:03+00:00 2026-05-23T10:05:03+00:00

Can anyone explain the following behaviour to me? >>> import numpy as np >>>

  • 0

Can anyone explain the following behaviour to me?

>>> import numpy as np
>>> {np.nan: 5}[np.nan]
5
>>> {float64(np.nan): 5}[float64(np.nan)]
KeyError: nan

Why does it work in the first case, but not in the second?
Additionally, I found that the following DOES work:

>>> a ={a: 5}[a]
float64(np.nan)
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T10:05:04+00:00Added an answer on May 23, 2026 at 10:05 am

    The problem here is that NaN is not equal to itself, as defined in the IEEE standard for floating point numbers:

    >>> float("nan") == float("nan")
    False
    

    When a dictionary looks up a key, it roughly does this:

    1. Compute the hash of the key to be looked up.

    2. For each key in the dict with the same hash, check if it matches the key to be looked up. This check consists of

      a. Checking for object identity: If the key in the dictionary and the key to be looked up are the same object as indicated by the is operator, the key was found.

      b. If the first check failed, check for equality using the __eq__ operator.

    The first example succeeds, since np.nan and np.nan are the same object, so it does not matter they don’t compare equal:

    >>> numpy.nan is numpy.nan
    True
    

    In the second case, np.float64(np.nan) and np.float64(np.nan) are not the same object — the two constructor calls create two distinct objects:

    >>> numpy.float64(numpy.nan) is numpy.float64(numpy.nan)
    False
    

    Since the objects also do not compare equal, the dictionary concludes the key is not found and throws a KeyError.

    You can even do this:

    >>> a = float("nan")
    >>> b = float("nan")
    >>> {a: 1, b: 2}
    {nan: 1, nan: 2}
    

    In conclusion, it seems a saner idea to avoid NaN as a dictionary key.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Can anyone explain the following behaviour to a relative newbie... const char cInputFilenameAndPath[] =
Can anyone explain what the following PHP Code does function query($query_string) { if ($query_string
Anyone can explain in details what the following macro does? #define write_XDATA(address,value) (((char *)0x010000)
Can anyone explain why the following code does not compile (on g++ (GCC) 3.2.3
Can anyone explain the following behaviour to me? When a field type in an
Can anyone explain the following behavior? var ctx = $('#myCanvas').getContext(2d); //doesnt work var ctx
Can anyone explain to me what does the following Ruby code do? VARIABLE.scan /\((.+)\)$/
Can anyone explain why following code won't compile? At least on g++ 4.2.4. And
Can anyone explain the following PHP Code ? function get_param($param_name, $param_type = 0) {
Can anyone explain why the following jquery only fires the 2nd toggle event and

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.