Activity

1. max-muoto

   added

   docsDocumentation in the Doc dirDocumentation in the Doc dir

   on Jul 4, 2024
2. serhiy-storchaka commented on Jul 4, 2024

   

   serhiy-storchaka

   on Jul 4, 2024

   Member

   More actions

   The __replace__ method itself is an implementation detail. Only the support of copy.replace() should be documented. In future we may add other ways to specify this.

   Special methods like __iter__ or __reduce__ are rarely documented. Instead the fact that objects are iterable or pickleable are documented.
3. max-muoto commented on Jul 5, 2024

   

   max-muoto

   on Jul 5, 2024

   ContributorAuthor

   More actions

   The __replace__ method itself is an implementation detail. Only the support of copy.replace() should be documented. In future we may add other ways to specify this.

   Special methods like __iter__ or __reduce__ are rarely documented. Instead the fact that objects are iterable or pickleable are documented.

   Makes sense, I will just say it just being documented in copy, while it needing to be special-cased I think makes it harder to realize that type-checkers should likely implement support - so I do wonder if there's a better way to indicate things like that long-term.
4. randolf-scholz commented on Jul 1, 2025

   

   randolf-scholz

   on Jul 1, 2025

   Last edited by randolf-scholz

   Contributor

   More actions

   @max-muoto Regarding copy.replace in conjunction with generic types, is the following considered legal?

   import copy
   from dataclasses import dataclass
   
   @dataclass
   class Foo[T]:
       value: T
   
   foo: Foo[int] = Foo(1)
   copy.replace(foo, value="x")  # <-- mutates generic type into Foo[str]

   Or, should copy.replace only allow integer values for value in this case? This would be useful to add to the documentation as well.

   context: https://discuss.python.org/t/make-replace-stop-interfering-with-variance-inference/96092/16