[Python-Dev] configparser: should optionxform be idempotent?
Greg Ewing
greg.ewing at canterbury.ac.nz
Thu Mar 7 18:56:13 EST 2019
More information about the Python-Dev mailing list
Thu Mar 7 18:56:13 EST 2019
- Previous message (by thread): [Python-Dev] configparser: should optionxform be idempotent?
- Next message (by thread): [Python-Dev] configparser: should optionxform be idempotent?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Paul Moore wrote:
> There's a subtle difference in the mathematical
> and computing meanings [of idempotent] (around functions
> with side-effects, which aren't a thing in maths)
Not really an issue here, since optionxform shouldn't be having
side effects if it's sane.
In any case, the word is easy enough to avoid in this case.
We could say something like:
"The optionxform function transforms option names to a
canonical form. If the name is already in canonical form,
it should be returned unchanged."
--
Greg
- Previous message (by thread): [Python-Dev] configparser: should optionxform be idempotent?
- Next message (by thread): [Python-Dev] configparser: should optionxform be idempotent?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list