[issue41276] Min / Max returns different values depending on parameter order

Steven D'Aprano added the comment: This is correct behaviour. What makes you think otherwise? For future bug reports, please don't post screen shots of text, copy and paste the text into the body of your bug report. Posting screenshots makes it difficult for us to copy and run your code, and

[issue41276] Min / Max returns different values depending on parameter order

Steven D'Aprano added the comment: In your first example, `min([(-5, 2), (0, 2)])` the min() function compares the two tuples and finds that the first one is lexicographically smaller: py> (-5, 2) < (0, 2) True so (-5, 2) is considered the minimum. In the second example, using the ke

[issue41276] Min / Max returns different values depending on parameter order

Calvin Davis added the comment: Thank you for the clarification, sorry for the report! You're awesome! -- ___ Python tracker ___ __

[issue41277] documentation: os.setxattr() errno EEXIST and ENODATA

New submission from Pablo Dumas : Shouldn't os.setxattr() errno EEXIST be when "XATTR_CREATE was specified, and the attribute exists already" and errno ENODATA be when "XATTR_REPLACE was specified, and the attribute does not exist."? In the current os module documentation, it's the other way

[issue41236] "about" button in MacOS caused an error

Ned Deily added the comment: Terry, based on the error message provided, i.e. "About Widget Demo", I assumed that the poster was not using IDLE here. But we can't tell without more input. "when I run 3.9 test.pythoninfo, I am asked to install gcc tools and maybe xcode. Is this expected?" W

<    1   2