Changes by Matt Joiner anacro...@gmail.com:
--
nosy: +anacrolix
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9528
___
___
Python-bugs-list
Éric Araujo mer...@netwok.org added the comment:
Alan: the Versions field is used to mark versions that will get a patch, not
all versions affected.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9528
STINNER Victor victor.stin...@haypocalc.com added the comment:
@alanjds: Why do you add Python 2.7 version to this issue?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9528
___
Brett Cannon br...@python.org added the comment:
@Victor it doesn't really matter why since it is an incorrect classification.
This issue in no way involves Python 2.7 since we will not backport any modules
to Python 2.7.
--
versions: +Python 3.3 -Python 2.7, Python 3.2
Alan Justino alan.just...@yahoo.com.br added the comment:
@haypo: Because it affects version 2.7 too.
@Victor: Even since we will not backport any modules to Python 2.7, is not
worth to sign that this affects it too? Even wontfix or rejected, it affects,
does not?
Have I made something
Alan Justino alan.just...@yahoo.com.br added the comment:
(noticed a typo at the start of my last msg: @Victor should be @brett.cannon)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9528
Marc-Andre Lemburg m...@egenix.com added the comment:
Alan Justino wrote:
I am getting a hard time trying to do some BDD with c-based datetime because
I cannot mock it easily to force datetime.datetime.now() to return a desired
value, making almost impossible to test time-based code, like
Changes by Alan Justino alan.just...@yahoo.com.br:
--
nosy: +alanjds
versions: +Python 2.7
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9528
___
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
BDFL and python-dev were opposed to this idea.
--
resolution: - rejected
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
On Thu, Aug 12, 2010 at 10:26 PM, STINNER Victor rep...@bugs.python.org wrote:
..
1. Datetime.py time source (time.time()) represents time as
a floating point number which leads to system dependent behavior
and
STINNER Victor victor.stin...@haypocalc.com added the comment:
1. Datetime.py time source (time.time()) represents time as
a floating point number which leads to system dependent behavior
and introduces floating point operations where they are not needed.
Why not introducing a new function
Marc-Andre Lemburg m...@egenix.com added the comment:
I believe _time module should become the home of the gettimeofday() method
and pure python implementation of time.time() will be
def time()
s, us = _time.gettimeofday()
return s + 1e-6 * us
Similarly time.sleep() can be
Raymond Hettinger rhettin...@users.sourceforge.net added the comment:
These changes are very aggressive and may be doing more harm than good.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9528
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
On Fri, Aug 6, 2010 at 3:44 AM, Marc-Andre Lemburg
rep...@bugs.python.org wrote:
..
Why are you calling the ticket *Add* pure Python implementation of time
module to CPython when you appear to be after *replacing* the C
New submission from Alexander Belopolsky belopol...@users.sourceforge.net:
The original RFE at issue 7989 was:
After discussion on numerous issues, python-dev, and here at the PyCon sprints,
it seems to be a good idea to move timemodule.c to _timemodule.c and convert as
much as possible into
15 matches
Mail list logo