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 schof
Recipients eric.araujo, georg.brandl, l0nwlf, loewis, pitrou, schof, twhitema
Date 2010-05-09.03:08:12
SpamBayes Score 0.0021625925
Marked as misclassified No
Message-id <1273374494.87.0.249220974382.issue8350@psf.upfronthosting.co.za>
In-reply-to
Content
Please don't close this as "invalid."

Most (all?) of the functions in the os module have positional-only arguments, which are documented in exactly the same manner as arguments which can be supplied using a keyword.

As someone reading the documentation, how am I supposed to know which arguments can be supplied with keywords and which can't?

This ticket and the link to http://docs.python.org/dev/reference/expressions.html#calls are helpful in explaining this now, but I would NEVER have thought to look there to find out why os.fdopen isn't working the way it's documented. Requiring me to experiment to determine which function works which way seems to miss the point of having documentation in the first place.

I take no position on whether this should be fixed with a documentation change or a code change, but it should be fixed. If the consensus is that a documentation change would be quicker to implement, I'm happy to submit a doc patch.
History
Date User Action Args
2010-05-09 03:08:15schofsetrecipients: + schof, loewis, georg.brandl, pitrou, eric.araujo, twhitema, l0nwlf
2010-05-09 03:08:14schofsetmessageid: <1273374494.87.0.249220974382.issue8350@psf.upfronthosting.co.za>
2010-05-09 03:08:13schoflinkissue8350 messages
2010-05-09 03:08:12schofcreate