[issue44651] An unclear definition in Doc/glossary.rst

Mark Dickinson added the comment: Closing. @StevenHsuYL: Thank you for the contribution! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue44651] An unclear definition in Doc/glossary.rst

Mark Dickinson added the comment: New changeset c05a790693b3b00ac7cb5b96ad416ca9d8ecb14a by Steven Hsu in branch 'main': bpo-44651: delete entry of "coercion" in Doc/glossary.rst (GH-27226) https://github.com/python/cpython/commit/c05a790693b3b00ac7cb5b96ad416ca9d8ecb14a -- ___

[issue44651] An unclear definition in Doc/glossary.rst

Mark Dickinson added the comment: My one worry with removing the entry is that documentation of other projects may be referring to it via intersphinx. If we think this is likely to be a real problem, we could leave a stub entry, but I think it's okay to go ahead and delete. To be on the saf

[issue44651] An unclear definition in Doc/glossary.rst

Change by Steven Hsu : -- keywords: +patch pull_requests: +25767 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27226 ___ Python tracker ___ _

[issue44651] An unclear definition in Doc/glossary.rst

Jack DeVries added the comment: @StevenHsuYL yes, you can go ahead and create a PR for this if you'd like! Just follow the directions in the dev guide (link in sidebar). I can't really tell for sure because I'm on my phone right now, but it looks like this might be your first time contributi

[issue44651] An unclear definition in Doc/glossary.rst

Steven Hsu added the comment: Thanks for your reply and suggestion. I can totally understand your explanation about the definition of coercion. In conclusion, I think this glossary entry may need some modification for better understanding, or simply be deleted. So what's the next step? Shou

[issue44651] An unclear definition in Doc/glossary.rst

Terry J. Reedy added the comment: OK with me. -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue44651] An unclear definition in Doc/glossary.rst

Mark Dickinson added the comment: Searching further, none of the uses of "coerce" or "coercion" in the docs seem to be a good match for the definition in this glossary entry. For example, from ipaddress.rst: > By default, attempting to create a network object with host bits set will result i

[issue44651] An unclear definition in Doc/glossary.rst

Mark Dickinson added the comment: Agreed that "of the same type" part is confusing. I suspect the intended meaning was that the operation *expects* both arguments to have the same type, so if the actual arguments have different types then they have to be coerced to a common type. In the exam

[issue44651] An unclear definition in Doc/glossary.rst

Change by Serhiy Storchaka : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue44651] An unclear definition in Doc/glossary.rst

New submission from Steven Hsu : In Doc/glossary.rst, the definition about "coercion" is as below: "The implicit conversion of an instance of one type to another during an operation which involves two arguments of the same type." However, in the example following this definition, it shows the