Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #29070 > unrolled thread
| Started by | readmax <readmax@hushmail.com> |
|---|---|
| First post | 2012-09-13 19:06 +0000 |
| Last post | 2012-09-13 19:06 +0000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: datetime readmax <readmax@hushmail.com> - 2012-09-13 19:06 +0000
| From | readmax <readmax@hushmail.com> |
|---|---|
| Date | 2012-09-13 19:06 +0000 |
| Subject | Re: datetime |
| Message-ID | <mailman.631.1347563197.27098.python-list@python.org> |
Terry Reedy <tjreedy <at> udel.edu> writes: > You did not specify *which* time to set, but ... > > If you mean time.clock_shift(clk_id, shift_seconds), no. > > time.clock_settime(clk_id, time.clock_gettime(clk_id) + delta_seconds) > I am talking about the system-wide clock on Debian. What should I use as "clk_id"? BTW, if by "version 3.3" you mean python 3, I am only using 2.x.
Back to top | Article view | comp.lang.python
csiph-web