On Wed, Oct 27, 2021 at 6:15 AM Paul Moore <p.f.mo...@gmail.com> wrote: > Having the code stop working just because I changed the way the called > function handles its defaults would be a nuisance (again, I'm not > saying this would happen often, just that I could easily imagine it > happening if this feature was available). The function f might well be > from a library, or a script, that I wrote for something else, and it > might be perfectly reasonable to use the new feature for that other > use case.
The same will be true if it changes from "x=None" to "x=_sentinel". Every change breaks someone's workflow. I think Python would benefit from a "map these arguments to that function signature" tool, but that's independent of this proposal. Don't want to have massive scope creep here. ChrisA _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/BIEKFSLPA4OBPZAATTZTZKFL2XGA5UXU/ Code of Conduct: http://python.org/psf/codeofconduct/
