[issue4018] "for me" installer problem on x64 Vista

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > existis a 2.6 fix or a build with fix? No, this will be fixed in 2.6.1. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4018] "for me" installer problem on x64 Vista

Waldecir <[EMAIL PROTECTED]> added the comment: existis a 2.6 fix or a build with fix? -- nosy: +psycoman ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue4018] "for me" installer problem on x64 Vista

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Thanks for the confirmation. Committed as r66881, r66882, and r66883. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue4018] "for me" installer problem on x64 Vista

Steve Lee <[EMAIL PROTECTED]> added the comment: Works for me on Vista, Not tried on XP. Seems a reasonable temporary compromise though we are now stopping all possibility of an 'all' install but as noted there is probably little need for it when application installers are created.

[issue4018] "for me" installer problem on x64 Vista

Changes by Martin v. Löwis <[EMAIL PROTECTED]>: -- keywords: +needs review priority: normal -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue4018] "for me" installer problem on x64 Vista

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Here is a patch that fixes the problem as proposed. An installer built with that patch is available from http://www.dcl.hpi.uni-potsdam.de/home/loewis/u/python-3.0.14158.msi -- keywords: +patch Added file: http://bugs.python.org/fil

[issue4018] "for me" installer problem on x64 Vista

Steve Lee <[EMAIL PROTECTED]> added the comment: The mozilla bug is https://bugzilla.mozilla.org/show_bug.cgi?id=371359 but looking at it now, especially comment 4, it's not much help. ___ Python tracker <[EMAIL PROTECTED]> _

[issue4018] "for me" installer problem on x64 Vista

Steve Lee <[EMAIL PROTECTED]> added the comment: I spotted the problem on Vista Home Premium SP1 32bit As John indicates the problem with the 'all users' install is that it requires elevation to run as admin even if logged in as an administrator. That is rather non obvious (John suggests running

[issue4018] "for me" installer problem on x64 Vista

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > May be call of SetDllDirectory with argument path to python executable > before to load a python module may help. I'm skeptical. According to the documentation, "The directory from which the application loaded." is already in the search p

[issue4018] "for me" installer problem on x64 Vista

Armando Rowe <[EMAIL PROTECTED]> added the comment: See issue 4022 for a similar problem in WIndows XP professional, installed for all users. -- nosy: +armandorowe ___ Python tracker <[EMAIL PROTECTED]> _

[issue4018] "for me" installer problem on x64 Vista

Roumen Petrov <[EMAIL PROTECTED]> added the comment: May be call of SetDllDirectory with argument path to python executable before to load a python module may help. -- nosy: +rpetrov ___ Python tracker <[EMAIL PROTECTED]>

[issue4018] "for me" installer problem on x64 Vista

John Ehresman <[EMAIL PROTECTED]> added the comment: > I don't think this could even work: apparently, Vista disallows putting > a path into the name field. So extension modules will have to ship with > their own copy of the CRT (or link statically). I agree that this is the case. The closest t

[issue4018] "for me" installer problem on x64 Vista

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > I looked for > a solution to this, but so far can't find any -- and this would also > mean that .pyd files in site-packages and elsewhere would need .manifest > files that contain the path to where msvcr90.dll is located. I don't think

[issue4018] "for me" installer problem on x64 Vista

John Ehresman <[EMAIL PROTECTED]> added the comment: I think one of the tested machines is Vista RTM, though it's been updated. I also tried of Vista x32 SP1 and it fails there. If non-admin installs can't be made to work, I agree that the "for me" option be dropped and the installer changed

[issue4018] "for me" installer problem on x64 Vista

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: I had noticed the problem myself, and I don't know any solution to it. It's still part of the aftermath of switching to VS 2008, maybe we should have stayed with VS 2003 :-( Out of curiosity: Is this Vista SP1? If so, can somebody try Vista

[issue4018] "for me" installer problem on x64 Vista

Changes by Steve Lee <[EMAIL PROTECTED]>: -- nosy: +slee ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing list Un

[issue4018] "for me" installer problem on x64 Vista

Christian Heimes <[EMAIL PROTECTED]> added the comment: I don't have a Vista box at my disposal. Martin might be able to help you. Barry: I've marked this bug as blocker because it makes Vista installations useless. It's not a blocker for the upcoming beta but it should be fixed before the next

[issue4018] "for me" installer problem on x64 Vista

John Ehresman <[EMAIL PROTECTED]> added the comment: Neither "..\\msvcr90.dll" or a full path work (with \ or \\) seem to work. ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue4018] "for me" installer problem on x64 Vista

Christian Heimes <[EMAIL PROTECTED]> added the comment: Could you try it again with "..\\msvcr90.dll", please? -- nosy: +christian.heimes ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4018] "for me" installer problem on x64 Vista

Changes by Christian Heimes <[EMAIL PROTECTED]>: -- assignee: -> loewis nosy: +loewis priority: -> critical ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue4018] "for me" installer problem on x64 Vista

New submission from John Ehresman <[EMAIL PROTECTED]>: After installing the 32 bit .msi or the 64 bit .msi "for me" on a fairly clean Vista x64 machine, the socket module won't import because of a side-by-side configuration error. The output below is from the 32 bit build. Microsoft Windows [Ve