raise TypeError when `__iter__` method is `None` by elmjag · Pull Request #7092 · RustPython/RustPython · GitHub
Skip to content

raise TypeError when __iter__ method is None#7092

Closed
elmjag wants to merge 1 commit intoRustPython:mainfrom
elmjag:iter-meth-none
Closed

raise TypeError when __iter__ method is None#7092
elmjag wants to merge 1 commit intoRustPython:mainfrom
elmjag:iter-meth-none

Conversation

@elmjag
Copy link
Copy Markdown
Contributor

@elmjag elmjag commented Feb 12, 2026

Setting special __iter__ method to None is used to mark objects as non-iterable.

https://docs.python.org/3/reference/datamodel.html#special-method-names

Check if __iter__ is set to None and raise TypeError exception.

Summary by CodeRabbit

  • Bug Fixes
    • Enhanced error reporting for iteration operations with clearer, more precise error messages when attempting to iterate over non-iterable objects
    • Improved exception handling to distinguish between different iteration failure scenarios

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 12, 2026

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@crates/vm/src/types/slot.rs`:
- Around line 548-551: Replace the AttributeError raised when __iter__ is
missing with a TypeError: in the block that calls vm.get_special_method(&zelf,
identifier!(vm, __iter__)), change the ok_or_else(...) from
vm.new_attribute_error(...) to vm.new_type_error(...) and construct the message
as "'<ClassName>' object is not iterable" using the object's class name (e.g.,
format!("'{}' object is not iterable", zelf.class().name())). Keep the existing
method_is_none() TypeError behavior unchanged.
🧹 Nitpick comments (2)
crates/vm/src/types/slot.rs (2)

545-551: Decorative comment separators violate coding guidelines.

Lines 545–547 and 553–556 use blank // lines as section separators. As per coding guidelines, "Do not add decorative section separators (e.g. // -----------, // ===, /* *** */). Use /// doc-comments or short // comments only when they add value."

Proposed fix: collapse to single-line comments
-    //
-    // look-up '__iter__' method
-    //
+    // Look up __iter__ method
     let method_ident = identifier!(vm, __iter__);
     let method = vm
         .get_special_method(&zelf, method_ident)?
         .ok_or_else(|| vm.new_attribute_error(method_ident.as_str().to_owned()))?;

-    //
-    // setting '__iter__' method to 'None' value is used
-    // to mark non-iterable objects, raise TypeError
-    //
+    // __iter__ = None marks non-iterable objects
     if method_is_none(&method, vm) {

537-562: Consider consistency with __hash__ = None handling.

The __hash__ = None case (lines 758–783) is handled at slot-update time by storing hash_not_implemented as the slot function. The __iter__ = None case is handled at call time inside the wrapper. Both approaches work, but the inconsistency may confuse future maintainers. If there's no strong reason to differ, consider aligning the pattern (e.g., storing a dedicated iter_not_implemented function during slot update, similar to hash_not_implemented).

That said, CPython's slot_tp_iter also checks at call time, so the current approach is arguably more faithful to CPython.

Comment on lines +548 to +551
let method_ident = identifier!(vm, __iter__);
let method = vm
.get_special_method(&zelf, method_ident)?
.ok_or_else(|| vm.new_attribute_error(method_ident.as_str().to_owned()))?;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify what error CPython raises when __iter__ is dynamically deleted after being set
# Also check how get_special_method works and what it returns for None vs missing

echo "=== Check get_special_method implementation ==="
ast-grep --pattern 'fn get_special_method($$$) {
  $$$
}'

echo ""
echo "=== Look for get_special_method definition ==="
rg -n 'fn get_special_method' crates/vm/src/ -A 20 | head -50

Repository: RustPython/RustPython

Length of output: 1467


🏁 Script executed:

#!/bin/bash
echo "=== Check iter_wrapper and surrounding context in slot.rs ==="
rg -n 'iter_wrapper\|__iter__' crates/vm/src/types/slot.rs -B 5 -A 10

Repository: RustPython/RustPython

Length of output: 126


🏁 Script executed:

#!/bin/bash
echo "=== Check how other slot wrappers handle missing methods ==="
rg -n 'new_attribute_error|new_type_error' crates/vm/src/types/slot.rs -B 3 -A 1 | head -100

Repository: RustPython/RustPython

Length of output: 4724


🏁 Script executed:

#!/bin/bash
echo "=== Check if there are references to 'not iterable' error messages ==="
rg -n 'not iterable' crates/vm/src/ -B 2 -A 2

Repository: RustPython/RustPython

Length of output: 1234


🏁 Script executed:

#!/bin/bash
echo "=== Check get_special_method behavior in the codebase ==="
rg -n 'get_special_method.*ok_or' crates/vm/src/ -B 3 -A 3 | head -60

Repository: RustPython/RustPython

Length of output: 122


Change error type from AttributeError to TypeError when __iter__ is missing.

The code at line 551 currently raises AttributeError when get_special_method returns None (i.e., when __iter__ is not found). This is inconsistent with CPython, which raises TypeError: '<ClassName>' object is not iterable. This error type also aligns with how other slot wrappers in the codebase handle missing methods—len_wrapper, repr_wrapper, str_wrapper, and others all use new_type_error() for similar cases.

The method_is_none() check at line 557 handles the case where __iter__ exists but returns None, which should also raise the same TypeError (already correct).

Proposed fix
     let method_ident = identifier!(vm, __iter__);
     let method = vm
         .get_special_method(&zelf, method_ident)?
-        .ok_or_else(|| vm.new_attribute_error(method_ident.as_str().to_owned()))?;
+        .ok_or_else(|| vm.new_type_error(format!("'{}' object is not iterable", zelf.class().name())))?;
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
let method_ident = identifier!(vm, __iter__);
let method = vm
.get_special_method(&zelf, method_ident)?
.ok_or_else(|| vm.new_attribute_error(method_ident.as_str().to_owned()))?;
let method_ident = identifier!(vm, __iter__);
let method = vm
.get_special_method(&zelf, method_ident)?
.ok_or_else(|| vm.new_type_error(format!("'{}' object is not iterable", zelf.class().name())))?;
🤖 Prompt for AI Agents
In `@crates/vm/src/types/slot.rs` around lines 548 - 551, Replace the
AttributeError raised when __iter__ is missing with a TypeError: in the block
that calls vm.get_special_method(&zelf, identifier!(vm, __iter__)), change the
ok_or_else(...) from vm.new_attribute_error(...) to vm.new_type_error(...) and
construct the message as "'<ClassName>' object is not iterable" using the
object's class name (e.g., format!("'{}' object is not iterable",
zelf.class().name())). Keep the existing method_is_none() TypeError behavior
unchanged.

@ShaharNaveh
Copy link
Copy Markdown
Contributor

Thanks for the PR!
I don't think that the failed CI is related to your change, I'll investigate

@ShaharNaveh
Copy link
Copy Markdown
Contributor

yup: rust-lang/miri#4855

@ShaharNaveh ShaharNaveh mentioned this pull request Feb 12, 2026
@elmjag
Copy link
Copy Markdown
Contributor Author

elmjag commented Feb 12, 2026

yup: rust-lang/miri#4855

Thanks for investigating!

@ShaharNaveh
Copy link
Copy Markdown
Contributor

@elmjag please merge main, it should pass now

@elmjag
Copy link
Copy Markdown
Contributor Author

elmjag commented Feb 12, 2026

537-562: Consider consistency with __hash__ = None handling.
The __hash__ = None case (lines 758–783) is handled at slot-update time by storing hash_not_implemented as the slot function. The __iter__ = None case is handled at call time inside the wrapper. Both approaches work, but the inconsistency may confuse future maintainers. If there's no strong reason to differ, consider aligning the pattern (e.g., storing a dedicated iter_not_implemented function during slot update, similar to hash_not_implemented).
That said, CPython's slot_tp_iter also checks at call time, so the current approach is arguably more faithful to CPython.

I'll look into using this approach for __iter__ = None case. Sounds like a better way to implement it, marking this PR as draft for now.

@elmjag elmjag marked this pull request as draft February 12, 2026 15:20
Setting special `__iter__` method to `None` is used to mark
objects as non-iterable.

https://docs.python.org/3/reference/datamodel.html#special-method-names

Check if `__iter__` is set to `None` and raise TypeError exception.
@github-actions
Copy link
Copy Markdown
Contributor

📦 Library Dependencies

The following Lib/ modules were modified. Here are their dependencies:

[x] lib: cpython/Lib/typing.py
[ ] test: cpython/Lib/test/test_typing.py (TODO: 6)
[x] test: cpython/Lib/test/test_type_aliases.py
[x] test: cpython/Lib/test/test_type_annotations.py (TODO: 1)
[x] test: cpython/Lib/test/test_type_params.py (TODO: 10)
[x] test: cpython/Lib/test/test_genericalias.py

dependencies:

  • typing

dependent tests: (12 tests)

  • typing: test_annotationlib test_builtin test_enum test_fractions test_functools test_genericalias test_grammar test_isinstance test_type_aliases test_type_params test_types test_typing

Legend:

  • [+] path exists in CPython
  • [x] up-to-date, [ ] outdated

@ShaharNaveh
Copy link
Copy Markdown
Contributor

@elmjag can you please resolve the conflicts? I think it can be merged

@elmjag
Copy link
Copy Markdown
Contributor Author

elmjag commented Feb 23, 2026

@elmjag elmjag closed this Feb 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants