Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #29089 > unrolled thread
| Started by | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| First post | 2012-09-13 19:28 -0400 |
| Last post | 2012-09-13 19:28 -0400 |
| 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 Terry Reedy <tjreedy@udel.edu> - 2012-09-13 19:28 -0400
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2012-09-13 19:28 -0400 |
| Subject | Re: datetime |
| Message-ID | <mailman.650.1347578956.27098.python-list@python.org> |
On 9/13/2012 3:06 PM, readmax wrote: > 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"? Read the doc. > BTW, if by "version 3.3" you mean python 3 x.y in the doc means pythonx.y -- Terry Jan Reedy
Back to top | Article view | comp.lang.python
csiph-web