➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author w0rthle$$
Recipients w0rthle$$
Date 2020-07-11.05:45:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1594446359.56.0.57719330174.issue41277@roundup.psfhosted.org>
In-reply-to
Content 
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 around: "If XATTR_REPLACE is given and the attribute does not exist, EEXISTS will be raised. If XATTR_CREATE is given and the attribute already exists, the attribute will not be created and ENODATA will be raised."... Thanks!
History
Date User Action Args
2020-07-11 05:45:59w0rthle$$setrecipients: + w0rthle$$
2020-07-11 05:45:59w0rthle$$setmessageid: <1594446359.56.0.57719330174.issue41277@roundup.psfhosted.org>
2020-07-11 05:45:59w0rthle$$linkissue41277 messages
2020-07-11 05:45:59w0rthle$$create