[issue2149] Queue.maxsize, __init__() accepts any value as maxsize
rbp added the comment: For what it's worth, I do think this is an issue. As it currently stands, not only does the module silently accept invalid values, but the mutex issue exists (and is also silently ignored) if an object returning dynamic values is passed as maxsize. IMHO, the waters are already muddy, it's just that the mud is blue so everything seems alright :) I think zanella's patch is the way to go, even if it requires adding a setter method. ------ nosy: +rbp __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2149> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1040026] os.times() is bogus
rbp added the comment: Malte, Antoine and I discussed this a bit on #python-dev and concluded that the correct behaviour should be trying sysconf first, then HZ, or raise an exception if not even HZ is available (since whichever static value we chose would be misleading anyway). I'm attaching a patch (modified from Malte's) which implements that. -- nosy: +rbp versions: +Python 2.5, Python 2.6 Added file: http://bugs.python.org/file9514/os_times2.PATCH _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1040026> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1040026] os.times() is bogus
rbp added the comment: Malte noticed that my previous patch won't compile when HAVE_SYSCONFIG and HZ are not defined. My bad, silly mistake. I've attached a new version, which compiles and has been tested on all three cases (with test_posix4.PATCH). Please, someone with privileges remove os_times2.PATCH. Added file: http://bugs.python.org/file9518/os_times3.PATCH _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1040026> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
