Fix model_input_names singleton issue causing shared state #42051
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixes #42024
I found this while testing tokenizers - when you modify
model_input_nameson one tokenizer instance, it was affecting all other instances of the same tokenizer class.The problem is that
model_input_namesis defined as a class-level list, and in the__init__method (line 1417), when no custommodel_input_namesis provided, it was just referencing the class attribute directly instead of making a copy.So all instances were sharing the same list object. This is a classic Python gotcha with mutable class attributes.
The fix is simple - wrap it in
list()to create a new list for each instance:Before:
After:
This ensures each tokenizer instance gets its own independent copy of the list. Now modifications to one instance won't affect others.
The reproduction from the issue shows the problem clearly - with the fix, the second tokenizer instance will have the original list values instead of inheriting the modifications from the first instance.