[issue8350] os.mkdir doc comment is incorrect
John Mark Schofield added the comment: 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. -- nosy: +schof ___ Python tracker <http://bugs.python.org/issue8350> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8350] os.mkdir doc comment is incorrect
John Mark Schofield added the comment: I'd also suggest changing the title to "Documentation for many functions in os module is incomplete." I didn't because I don't know if that would be considered rude. (I'm new to the Python community.) -- ___ Python tracker <http://bugs.python.org/issue8350> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7481] Failing to start a thread leaves "zombie" thread in "initial" state
New submission from John Mark Schofield : SUMMARY: When you attempt to start a thread, and you're unable to (you get thread.error) it leaves a thread stuck in an "initial" state that never exits. (threading.enumerate() shows the threads and lists their status as "initial.") REPRODUCTION STEPS: See attached file. EXPECTED RESULT: Failing to start a thread should not leave the thread in an un-executable state. I would expect the thread start to either succeed or result in the thread being closed and GC'd. VERIFIED ON: Python 2.5.2 on OS X 10.5.8 Python 2.5.2 on Ubuntu 8.04 Python 2.5.4 on Windows XP Professional (Version 2002) SP3 Python 2.6.1 on OS X 10.6.2 -- files: repro_case.py messages: 96271 nosy: schof severity: normal status: open title: Failing to start a thread leaves "zombie" thread in "initial" state type: behavior versions: Python 2.5, Python 2.6 Added file: http://bugs.python.org/file15527/repro_case.py ___ Python tracker <http://bugs.python.org/issue7481> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
