[issue46882] Clarify argument type of platform.platform(aliased, terse) to boolean

Rotzbua added the comment: Thanks for pointing out the logical change from "true" to "True". I do not want to start a discussion about principles. Nevertheless I think a change from `platform(aliased=0, terse=0)` to `platform(aliased=False, terse=False)` makes the how-to-use more intuitive.

[issue46882] Clarify argument type of platform.platform(aliased, terse) to boolean

Change by Rotzbua : -- pull_requests: +29745 pull_request: https://github.com/python/cpython/pull/31621 ___ Python tracker ___ ___

[issue46882] Clarify argument type of platform.platform(aliased, terse) to boolean

Steven D'Aprano added the comment: See #46883 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46882] Clarify argument type of platform.platform(aliased, terse) to boolean

Steven D'Aprano added the comment: > Both arguments `aliased` and `terse` should be boolean instead of integer. Why should they be strictly True/False booleans? I disagree strongly that they should be. Any object that duck-types as a true or false value is sufficient. Treated as a

[issue46882] Clarify argument type of platform.platform(aliased, terse) to boolean

Change by Rotzbua : -- keywords: +patch pull_requests: +29742 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31617 ___ Python tracker ___

[issue46882] Clarify argument type of platform.platform(aliased, terse) to boolean

New submission from Rotzbua : Problem: Both arguments `aliased` and `terse` should be boolean instead of integer. Description: The function is as `platform.platform(aliased=0, terse=0)` so both arguments `aliased` and `terse` seems to be numbers. The documentation says: "If aliased is