Zachary Ware added the comment:
As all versions using the MSI installer are now out of support, I'm closing the
issue.
--
nosy: +zach.ware
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
Steve Dower added the comment:
I'm not exactly sure how msiexec does its parsing, but it's possible that
ALLUSERS=1 may not actually be the same as ALLUSERS=1. I use the latter
regularly with most versions of Python in existence and it works fine.
There may also be problems upgrading from the
Doug Rohm added the comment:
I realize this hasn't been commented on for a long time, but I'm noticing the
same issue trying to do a silent install with the 3.4.3 x64 windows installer.
The 3.4.2 x64 windows installer worked perfectly fine, but I can't seem to get
the registry and add/remove
Steve Dower added the comment:
The difference may be the ALLUSERS=1 option. Windows Installer is supposed to
auto-detect this when an installer is run as an admin, but maybe something in
our authoring is preventing this detection?
When I get a chance I'll try both and see if the logs show
Martin v. Löwis added the comment:
Steve: how is the auto-detection supposed to work, and what is the rationale?
Shouldn't it be possible that even someone with administrator privileges still
might want to install just for me? And how would they then specify that on
the command line, given
Steve Dower added the comment:
It's described at
http://msdn.microsoft.com/en-us/library/aa367559(v=vs.85).aspx, and frankly it
is incredibly confusing.
It is possible to reset ALLUSERS on the command line by specifying ALLUSERS=
--
___
Python
Martin v. Löwis added the comment:
Much of the text refers to Installer 5.0. msi.py currently targets installer
2.0. Does the auto-detection also work on such installers?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19351
Steve Dower added the comment:
No idea, TBH, though I'd guess that the behaviour comes from the installed
version of Windows Installer and the database schema comes from the authored
version.
Nonetheless, if the solution is to add ALLUSERS=1 to the command line when
doing silent all-user
Martin v. Löwis added the comment:
Jason: can you please report how exactly you attempted to perform the
installation?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19351
___
Martin v. Löwis added the comment:
I cannot reproduce the issue. In an elevated terminal, I run
msiexec /i python-3.4.1.amd64.msi /qn /l*v python.log ALLUSERS=1
Python installs fine, and does appear in the Remove programs panel.
--
___
Python
Steve Dower added the comment:
I've noticed this as well. I'm hoping to do a significant rework of the
installer for 3.5 and will keep this in mind, but I honestly have no idea how
to diagnose this in the current setup.
Windows Installer is responsible for the missing entries, and AFAIK the
Steve Dower added the comment:
This may actually be a Windows issue... the keys for uninstall are being
written to the Wow6432Node of the registry (on a 64-bit machine), and
apparently the Programs and Features panel does not read them from there.
The 64-bit installers should be fine (testing
Steve Dower added the comment:
Apparently keys in Wow6432Node are actually okay, so I'm not much closer to
figuring this out. As far as I can tell, the entry I have for Python 2.6.6
(which doesn't appear) has identical information to IronPython 2.7.4 (which
does appear).
--
Steve Dower added the comment:
Okay, now it looks to me like the install that 'works' ran under the SYSTEM
account while the one that didn't work ran under my (admin) user account.
This may be caused by running the installer from an elevated command prompt. If
it detects that it needs to
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: +steve.dower
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19351
___
New submission from Jason Bray:
Hello, I am working in an IT group, attempting to automate our management of
python. This issue applies to both Python 3.4 and Python 2.7.5 and Python 2.7.4
On a Windows machine (both 7 and 8.1 have been tested) when python msi's are
installed from the command
Changes by Christian Heimes li...@cheimes.de:
--
assignee: - loewis
components: +Windows
nosy: +loewis
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19351
___
17 matches
Mail list logo
