Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20975
___
___
Martin v. Löwis added the comment:
Bostjan: please understand that this is not possible. The build date is the
date when Python interpreter was actually built. If I build Python on my Linux
machine today, I get today's date. So there isn't any single one right build
date - on Unix, people
Martin v. Löwis added the comment:
I don't mind changing the text now, but I observe that there is a
chicken-and-egg problem with the hg changeset number. That changeset number is
only set when the tag is made, which must happen after the documentation is
updated (or else the updated
Geoffrey Spear added the comment:
There is no correct date and time Python 3.4 was built. I'm sure even the
Windows binary installers weren't built simultaneously, and on Linux systems it
will differ based on distro.
My Python 3.4 says it was built 5 minutes ago, because it was.
I suppose
Georg Brandl added the comment:
I'd just make it the approximate release date of 3.4. The version is adapted
anyway as part of a new minor release, so the date can also be.
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
Roundup Robot added the comment:
New changeset 4476b7493ee4 by Georg Brandl in branch '3.4':
Closes #20975: make date in the interpreter banner a little more consistent
http://hg.python.org/cpython/rev/4476b7493ee4
--
nosy: +python-dev
resolution: - fixed
stage: - committed/rejected
Boštjan Mejak added the comment:
I would change only the date and time. There was no Python 3.4 back in 2012 so
at least change the year. Well, my recommendation is this:
Python 3.4.0 (v3.4.0:04f714765c13, Mar 16 2014, 19:25:23) [MSC v.1600 64 bit
(AMD64)] on win32
Type help, copyright,
New submission from Boštjan Mejak:
Notice the wrong build info of Python 3.4 interpreter in the first code snippet
at http://docs.python.org/3/tutorial/interpreter.html#interactive-mode. I know
this snippet is just an example to show what does executing the command
python3.4 do, but still.
Éric Araujo added the comment:
I see two differences in my build, but I don’t think it’s really wrong, or that
it does harm. What exactly would you change?
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
