Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
Added ReST documentation. Will commit soon. Merging nosy list from issue 2736.
--
nosy: +Jay.Taylor, Neil Muller, amaury.forgeotdarc, andersjm, catlee,
davidfraser, erik.stephens, guettli, hodgestar, jribbens,
Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
Removed file: http://bugs.python.org/file25858/issue14908.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14908
___
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
I associated my commit with issue 2736 by mistake, but it is probably a good
thing because that issue contains a longer history.
Closing this as a duplicate.
--
resolution: - duplicate
stage: commit review -
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
Updated patch adds a few more tests and improves error handling in C
implementation.
--
nosy: +haypo
Added file: http://bugs.python.org/file25858/issue14908.diff
___
Python
Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
Removed file: http://bugs.python.org/file25854/issue14908.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14908
___
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
I think the attached patch implements what was agreed to on python-dev. We
need more tests, particularly around DST change. I tested the patch on OSX,
but I am interested to hear feedback from users of other OSes.
Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
--
assignee: - belopolsky
nosy: -Alexander.Belopolsky
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14908
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14908
___
___
Python-bugs-list mailing
Barry A. Warsaw ba...@python.org added the comment:
I completely agree. As easy (but obscure) as it is, it seems quite silly to
have to go through time.mktime(dt.timetuple())
--
___
Python tracker rep...@bugs.python.org
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
Barry,
Did you review the long discussion under issue 2736? Specifically, please
note the part about mxDateTime, ticks() and gmticks(). I am -0 on adding
ticks() and gmticks() and as far as I can tell no one has
Barry A. Warsaw ba...@python.org added the comment:
On Jun 04, 2012, at 03:45 PM, Alexander Belopolsky wrote:
Did you review the long discussion under issue 2736? Specifically, please
note the part about mxDateTime, ticks() and gmticks(). I am -0 on adding
ticks() and gmticks() and as far as
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
On Mon, Jun 4, 2012 at 11:57 AM, Barry A. Warsaw rep...@bugs.python.org wrote:
I've recently had to convert a bunch of code from using mxDateTime to
datetime+time,
That's a valuable experience. How big of a deal was the
Barry A. Warsaw ba...@python.org added the comment:
On Jun 04, 2012, at 04:03 PM, Alexander Belopolsky wrote:
That's a valuable experience. How big of a deal was the lack of
.ticks() and .gmticks()? How did you work around it?
It was *much* less of an issue than all the magic date format
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14908
___
___
Alexandre Zani alexandre.z...@gmail.com added the comment:
I think the easiest and most intuitive approach is to simply define timestamp()
as being the reverse of fromtimestamp(). Don't worry about leap seconds and all
that stuff.
If non-1970 epochs are a concern, this could be renamed to
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
On Mon, Jun 4, 2012 at 1:33 PM, Alexandre Zani rep...@bugs.python.org wrote:
I think the easiest and most intuitive approach is to simply define
timestamp()
as being the reverse of fromtimestamp().
I would like to invite
Alexandre Zani alexandre.z...@gmail.com added the comment:
I'm still reading through the issue you mentioned. (It's a painful read I have
to admit) One major obstacle seems to be that during the DST switch over, an
hour gets repeated and so the datetime object is ambiguous. (are you on the
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
On Mon, Jun 4, 2012 at 3:21 PM, Alexandre Zani rep...@bugs.python.org wrote:
Let me know if I misunderstood Alexander, but if I didn't this should be
documented with
the datetime object. Based upon my understanding, the
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
Barry,
I looked at your changeset at
http://bazaar.launchpad.net/~gwibber-committers/gwibber/trunk/revision/1354 and
at the specification at
http://developers.facebook.com/docs/reference/api/event/.
Am I correct that you
New submission from Dirkjan Ochtman dirk...@ochtman.nl:
There's datetime.fromtimestamp() and datetime.timetuple(), but no
datetime.timestamp(). It should be possible to round-trip a UNIX timestamp
through a datetime.datetime.
--
messages: 161558
nosy: djc
priority: normal
severity:
Changes by Antoine Pitrou pit...@free.fr:
--
components: +Library (Lib)
nosy: +belopolsky, lemburg
type: - enhancement
versions: +Python 3.3 -Python 2.7, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14908
Alexander Belopolsky alexander.belopol...@gmail.com added the comment:
See issue2736.
--
nosy: +Alexander.Belopolsky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14908
___
22 matches
Mail list logo
