Movatterモバイル変換
[0]ホーム
[Python-Dev] float atime/mtime/ctime - a bad idea?
Martin v. Loewismartin@v.loewis.de
16 Oct 2002 15:15:55 +0200
Guido van Rossum <guido@python.org> writes:> In this particular case, I think having a global flag should be good> enough. We can easily rig the standard library not to depend on its> value.Sounds good. Unless I hear otherwise, I'll add stat_float_times(bool).That still leaves the question of a migration plan, assuming thatusers, in general, would appreciate to silently get subsecondtimestamps where possible. Here is a proposal:- 2.3: just add stat_float_times. In the documentation, warn that the value will change in the future.- 2.4: make stat_float_times(True) the default. Applications that break would need to add stat_float_times(False) in a central place.This has no phase were a warning is emitted, but any scheme that addsa warning means that the user first has to add something (to silencethe warning), and then to remove something (when the default changes -although the option might stay forever).Regards,Martin
[8]ページ先頭