[issue13856] xmlrpc / httplib changes to allow for certificate verification

Senthil Kumaran added the comment: I think, I was using wrong terminology, by 'sending' I meant, 'using' the ca_file in the client to verify Server's certificates. -- ___ Python tracker __

[issue13882] Add format argument for time.time(), time.clock(), ... to get a timestamp as a Decimal object

STINNER Victor added the comment: Patch version 4, minor update: - remove the resolution field of _PyTime_t and remove int_log10(): use 1/divisior as the resolution to support divisor different than a power of 10 (e.g. the cpu frequency on Windows) - inline and remove _PyTime_FromTimespec()

[issue13882] Add format argument for time.time(), time.clock(), ... to get a timestamp as a Decimal object

Changes by STINNER Victor : -- assignee: -> Arfrever Added file: http://bugs.python.org/file24367/time_decimal-4.patch ___ Python tracker ___ ___

[issue13882] Add format argument for time.time(), time.clock(), ... to get a timestamp as a Decimal object

Changes by STINNER Victor : Removed file: http://bugs.python.org/file24330/time_decimal-2.patch ___ Python tracker ___ ___ Python-bugs-list ma

[issue13882] Add format argument for time.time(), time.clock(), ... to get a timestamp as a Decimal object

Changes by STINNER Victor : Removed file: http://bugs.python.org/file24331/time_decimal-3.patch ___ Python tracker ___ ___ Python-bugs-list ma

[issue13882] Add format argument for time.time(), time.clock(), ... to get a timestamp as a Decimal object

STINNER Victor added the comment: > Another possible format would be "tuple" Or, I forgot an obvious format: "datetime"! -- ___ Python tracker ___ _

[issue13882] Add format argument for time.time(), time.clock(), ... to get a timestamp as a Decimal object

Changes by STINNER Victor : -- assignee: Arfrever -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue13882] Add format argument for time.time(), time.clock(), ... to get a timestamp as a Decimal object

Changes by STINNER Victor : -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue11457] os.stat(): add new fields to get timestamps as Decimal objects with nanosecond resolution

STINNER Victor added the comment: I don't like the idea of adding new fields to os.stat() *by default* because it may break backward compatibility. And if the new fields are decimal.Decimal objects, the module has to be imported and it means that any call to os.stat() would be slower just to

[issue11457] os.stat(): add new fields to get timestamps as Decimal objects with nanosecond resolution

Arfrever Frehtes Taifersar Arahesis added the comment: I think that one of available types of time values returned by os.stat() should allow to directly pass these values to os.futimens() and os.utimensat(), which expect (time_sec, time_nsec) tuples. -- __

[issue9207] multiprocessing occasionally spits out exception during shutdown (_handle_workers)

Changes by Paul Nasrat : -- nosy: +pnasrat ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue4966] Improving Lib Doc Sequence Types Section

Terry J. Reedy added the comment: I agree with 3.3 only. This might not be ready for 3.2.3 anyway, depending on how soon hash patch is ready, and if not, it becomes a somewhat moot point as new people should then download 3.3.0 instead of 3.2.4 next August. -- ___

[issue4966] Improving Lib Doc Sequence Types Section

Georg Brandl added the comment: ISTM that not doing this will make maintenance harder. For 2.7 I agree that there is no clear boundary to make, but 3.2 should be split up as well to ease merging of updates. -- ___ Python tracker

[issue13703] Hash collision security issue

Zbyszek Szmek added the comment: What about PYTHONHASHSEED= -> off, PYTHONHASHSEED=0 -> random, PYTHONHASHSEED=n -> n ? I agree with Jim that it's better to have one env. variable than two. -- ___ Python tracker

[issue12892] UTF-16 and UTF-32 codecs should reject (lone) surrogates

Kang-Hao (Kenny) Lu added the comment: Attached patch does the following beyond what the patch from haypo does: * call the error handler * reject 0xd800~0xdfff when decoding utf-32 The followings are on my TODO list, although this patch doesn't depend on any of these and can be reviewed an

[issue13703] Hash collision security issue

Gregory P. Smith added the comment: > What about PYTHONHASHSEED= -> off, PYTHONHASHSEED=0 -> random, > PYTHONHASHSEED=n -> n ? I agree with Jim that it's better to have one > env. variable than two. Rather than the "" empty string for off I suggest an explicit string that makes it clear what th

<    1   2