[issue12046] Windows build identification incomplete

2012-06-19 Thread Georg Brandl

Georg Brandl ge...@python.org added the comment:

I guess this is not an issue anymore.

--
resolution:  - out of date
status: open - pending

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12046
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12046] Windows build identification incomplete

2012-06-19 Thread Martin v . Löwis

Martin v. Löwis mar...@v.loewis.de added the comment:

It's indeed resolved.

--
resolution: out of date - duplicate
status: pending - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12046
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12046] Windows build identification incomplete

2011-05-13 Thread Martin v . Löwis

Martin v. Löwis mar...@v.loewis.de added the comment:

I'd rather not patch the build process manually during a release, so probably 
there just won't be a hg build identification in the Windows binaries, then.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12046
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12046] Windows build identification incomplete

2011-05-12 Thread Georg Brandl

Georg Brandl ge...@python.org added the comment:

Martin, you're probably the only one who can fix this in reasonable time 
anyway.  So I'd not let it block 3.2.1.

(If all else fails, you can give the Windows build the correct identification 
manually, right?)

--
priority: release blocker - deferred blocker

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12046
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12046] Windows build identification incomplete

2011-05-11 Thread Martin v . Löwis

Martin v. Löwis mar...@v.loewis.de added the comment:

Ned: I agree this is desirable (i.e. the shipped binaries ought to carry proper 
build identification). I also think this is independent from this issue, 
though, since the changes to integrate build identification into the window 
build process won't be unrelated to any autoconf changes we may need.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12046
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12046] Windows build identification incomplete

2011-05-10 Thread Ned Deily

Ned Deily n...@acm.org added the comment:

Note, the Unix build only identifies itself like that if there is a working 
copy of hg on $PATH at configure time.  If not, the version string also 
silently defaults to default.  That requirement creates a bit of a problem 
for the OS X installer build script since hg is not currently shipped with OS X 
and the build script goes to some lengths to ensure that the build environment 
is not contaminated with non-system components, including setting PATH to 
standard system values.  It might also be an issue for some other Unix platform 
builds.  My preference would be to add an AC_PATH_PROG check or some such to 
configure.in to be able to specify an HG environment variable rather than 
having to open up PATH.  Comments?

--
nosy: +ned.deily

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12046
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12046] Windows build identification incomplete

2011-05-09 Thread Martin v . Löwis

New submission from Martin v. Löwis mar...@v.loewis.de:

The Unix build identifies itself with a string such as

Python 3.2.1b1 (3.2:5b34f84ca773, May 10 2011, 00:58:43)

and sys._mercurial then is ('CPython', '3.2', '5b34f84ca773')

In the Windows build, the identification is

Python 3.2.1b1 (default, May 10 2011, 00:33:43) [MSC v.1500 32 bit (Intel)] on 
win32

and sys._mercurial is ('CPython', '', '')

Not sure whether this is a release blocker, but it's definitely a step 
backwards from 3.2.0.

--
messages: 135664
nosy: georg.brandl, loewis
priority: release blocker
severity: normal
status: open
title: Windows build identification incomplete
versions: Python 3.2

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12046
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue12046] Windows build identification incomplete

2011-05-09 Thread Nadeem Vawda

Changes by Nadeem Vawda nadeem.va...@gmail.com:


--
nosy: +nadeem.vawda

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12046
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com