NetworkXError on incompatible key types after node label migration

What the upgrade actually broke

The NetworkX 2.x release series replaced the old G.nodes dict with a view that implements the mapping protocol but is not a built‑in dict. The view is still hash‑key based, so mixed hashable labels (e.g. "a" and 1) are perfectly legal. The NetworkXError you see is almost always a symptom of code that assumes G.nodes is a real dict and calls methods that the view does not expose (for example G.nodes.update() or isinstance(G.nodes, dict)). It can also appear if you pass the view itself to an API that expects a plain mapping and then tries to perform an operation that the view does not support.

Confirmed facts

• Node identifiers must be hashable; mixed types are allowed.
• In NetworkX 2.x G.nodes is a NodeView, not a dict.
• NetworkX 2.5 did not introduce a new storage format; the change was in the public API surface.
• No official compatibility shim was released for code that directly mutates G.nodes as a dict.
• The migration guide for 1.x→2.x covers the view change but does not add a separate 2.5 migration path.

Supported strategy for a clean upgrade

1. Verify hashability
   Ensure every node label you plan to keep is hashable:
   

   for n in G.nodes:
       if not isinstance(n, collections.abc.Hashable):
           raise ValueError(f"Unhashable node label: {n!r}")
   

2. Replace direct dict access with view API
   Use the mapping protocol provided by NodeView:
   • G.nodes[n] returns the attribute dict for node n.
   • G.nodes[n]["attr"] reads an attribute.
   • G.nodes[n].update({...}) or G.nodes[n]["attr"] = value to write.
   • To iterate over nodes and attributes use G.nodes(data=True) or G.nodes.items().
3. When a real dict is required
   Copy the view explicitly:
   

   node_dict = dict(G.nodes)
   # node_dict behaves like a normal dict
   

4. Adjust code that used G.nodes.update() or similar
   Replace such calls with a loop or G.add_nodes_from():

   for n, attrs in new_nodes:
       G.add_node(n, **attrs)
   

5. Run a quick consistency check
   After refactoring, validate that the graph still contains the expected edges and attributes:
   

   assert G.number_of_nodes() == expected_nodes
   assert G.number_of_edges() == expected_edges
   

Where to find official guidance

• The NetworkX 2.x documentation contains a NodeView section and migration notes for 1.x→2.x.
• There is no dedicated 2.5 migration guide beyond the general view change; the recommended approach is to treat G.nodes as an abstract mapping.
• Community resources (e.g., GitHub issues and StackOverflow) often provide snippets for converting code that used the old dict semantics.

What we still need to decide

To fine‑tune the recommendation, it would help to know which exact function or line of code is raising the NetworkXError after the upgrade. If the error originates from a third‑party library that still expects G.nodes to be a dict, the workaround may involve wrapping the view with dict(G.nodes) only for that call.