Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #67725 > unrolled thread
| Started by | MRAB <python@mrabarnett.plus.com> |
|---|---|
| First post | 2014-03-04 21:38 +0000 |
| Last post | 2014-03-04 21:38 +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: Proper conversion of timestamp MRAB <python@mrabarnett.plus.com> - 2014-03-04 21:38 +0000
| From | MRAB <python@mrabarnett.plus.com> |
|---|---|
| Date | 2014-03-04 21:38 +0000 |
| Subject | Re: Proper conversion of timestamp |
| Message-ID | <mailman.7744.1393969089.18130.python-list@python.org> |
On 2014-03-04 20:57, Igor Korot wrote: > Hi, ALL, > I'm getting this: > > timestamp out of range for platform localtime()/gmtime() function > > trying to convert the timestamp with milliseconds into the datetime object. > > The first hit of Google gives me this: > > http://stackoverflow.com/questions/12458595/convert-epoch-timestamp-in-python > > but the solution described is not good for me since it does not gives > me the milliseconds value. > > How do I get the proper datetime value including milliseconds from the > timestamp? > > Thank you. > Are you using Python 2? If yes, then try dividing by 1000.0.
Back to top | Article view | comp.lang.python
csiph-web