Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #65897 > unrolled thread

Re: [RELEASED] Python 3.4.0 release candidate 1

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [RELEASED] Python 3.4.0 release candidate 1 Terry Reedy <tjreedy@udel.edu> - 2014-02-11 05:13 -0500
    Re: [RELEASED] Python 3.4.0 release candidate 1 Duncan Booth <duncan.booth@invalid.invalid> - 2014-02-11 15:42 +0000
      Re: [RELEASED] Python 3.4.0 release candidate 1 Terry Reedy <tjreedy@udel.edu> - 2014-02-11 12:11 -0500
      Re: [RELEASED] Python 3.4.0 release candidate 1 Bob Hanson <d2mp1a9@newsguy.com> - 2014-02-12 11:42 -0800
      Re: [RELEASED] Python 3.4.0 release candidate 1 Terry Reedy <tjreedy@udel.edu> - 2014-02-12 18:48 -0500

#65897 — Re: [RELEASED] Python 3.4.0 release candidate 1

On 2/11/2014 2:43 AM, Larry Hastings wrote:
>
> On behalf of the Python development team, I'm delighted to announce
> the first release candidate of Python 3.4.

> To download Python 3.4.0rc1 visit:
>
>      http://www.python.org/download/releases/3.4.0/

I installed 64 bit 3.3.4 yesterday with no problem. I reran it today in 
repair mode and again, no problem.

With 64 bit 3.4.0, I get
"There is a problem with this Windows Installer package. A program 
required for the install to complete could not be run."

No, the generic message does not bother to say *which* program :-(.

34 bit 3.4.0 installed fine. I redownloaded 64bit 3.4.0 and install 
gives the same message.

Can someone verify that this is not some bizarre glitch on my machine?

If it is not, Windows users should download the 32 bit binary for now.

Someone should remove the link to the installer that does not work.

A followup should be posted when it is replaced.

-- 
Terry Jan Reedy

[toc] | [next] | [standalone]

#65920

Terry Reedy <tjreedy@udel.edu> wrote:

> On 2/11/2014 2:43 AM, Larry Hastings wrote:
>>
>> On behalf of the Python development team, I'm delighted to announce
>> the first release candidate of Python 3.4.
> 
>> To download Python 3.4.0rc1 visit:
>>
>>      http://www.python.org/download/releases/3.4.0/
> 
> I installed 64 bit 3.3.4 yesterday with no problem. I reran it today in 
> repair mode and again, no problem.
> 
> With 64 bit 3.4.0, I get
> "There is a problem with this Windows Installer package. A program 
> required for the install to complete could not be run."
> 
> No, the generic message does not bother to say *which* program :-(.
> 
> 34 bit 3.4.0 installed fine. I redownloaded 64bit 3.4.0 and install 
> gives the same message.
> 
> Can someone verify that this is not some bizarre glitch on my machine?
> 
I downloaded and installed it without problems on a 64bit Windows 7 system.
Maybe it is a bizarre glitch on your system, or perhaps it assumes 
something is present which is there on my system and missing on yours.

I see that part way through the install it downloads setuptools/pip from 
pypi. Did your system have network access?

What happens if you enable the installer log by running:

  msiexec /i python-3.4.0rc1.amd64.msi /L*v logfile.txt

Does it put any useful messages in logfile.txt?

-- 
Duncan Booth

[toc] | [prev] | [next] | [standalone]

#65930

On 2/11/2014 10:42 AM, Duncan Booth wrote:
> Terry Reedy <tjreedy@udel.edu> wrote:
>
>> On 2/11/2014 2:43 AM, Larry Hastings wrote:
>>>
>>> On behalf of the Python development team, I'm delighted to announce
>>> the first release candidate of Python 3.4.
>>
>>> To download Python 3.4.0rc1 visit:
>>>
>>>       http://www.python.org/download/releases/3.4.0/
>>
>> I installed 64 bit 3.3.4 yesterday with no problem. I reran it today in
>> repair mode and again, no problem.
>>
>> With 64 bit 3.4.0, I get
>> "There is a problem with this Windows Installer package. A program
>> required for the install to complete could not be run."
>>
>> No, the generic message does not bother to say *which* program :-(.
>>
>> 34 bit 3.4.0 installed fine. I redownloaded 64bit 3.4.0 and install
>> gives the same message.
>>
>> Can someone verify that this is not some bizarre glitch on my machine?
>>
> I downloaded and installed it without problems on a 64bit Windows 7 system.
> Maybe it is a bizarre glitch on your system, or perhaps it assumes
> something is present which is there on my system and missing on yours.

As I noted in response to David, starting completely clean allows 32 bit 
version to install, but not 64 bit version.

> I see that part way through the install it downloads setuptools/pip from
> pypi. Did your system have network access?

Enough to post the original message ;-). And yes, A box came up asking 
about that and I said yes.

> What happens if you enable the installer log by running:
>
>    msiexec /i python-3.4.0rc1.amd64.msi /L*v logfile.txt

A megabyte file with nearly 7000 lines

> Does it put any useful messages in logfile.txt?

'error' occurs on 40. most are like the following

MSI (s) (40:08) [11:57:25:973]: Package to be registered: 
'python-3.4.0rc1.amd64.msi'
MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: AdminProperties 3: 
-2147287038

Here is the one for the boxed message:

Action 11:57:26: RemovePip.
Action start 11:57:26: RemovePip.
MSI (s) (40:0C) [11:57:26:426]: Note: 1: 1721 2: RemovePip 3: 
C:\Programs\Python34\python.exe 4: -m ensurepip._uninstall
MSI (s) (40:0C) [11:57:26:426]: Note: 1: 2262 2: Error 3: -2147287038
Error 1721. There is a problem with this Windows Installer package. A 
program required for this install to complete could not be run. Contact 
your support personnel or package vendor. Action: RemovePip, location: 
C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall
MSI (s) (40:0C) [11:57:28:874]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (40:0C) [11:57:28:874]: Product: Python 3.4.0b2 (64-bit) -- 
Error 1721. There is a problem with this Windows Installer package. A 
program required for this install to complete could not be run. Contact 
your support personnel or package vendor. Action: RemovePip, location: 
C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall

MSI (c) (98:EC) [11:57:30:204]: PROPERTY CHANGE: Deleting SECONDSEQUENCE 
property. Its current value is '1'.
Action ended 11:57:30: ExecuteAction. Return value 3.
MSI (c) (98:EC) [11:57:30:204]: Doing action: FatalError
A

Can you make anything of these?

-- 
Terry Jan Reedy

[toc] | [prev] | [next] | [standalone]

#66086

[32-bit Windows XP-SP2]

On Tue, 11 Feb 2014 12:11:49 -0500, Terry Reedy wrote:

> [problems installing rc1]
>
> On 2/11/2014 10:42 AM, Duncan Booth wrote:
>
> > Does it put any useful messages in logfile.txt?
> 
> 'error' occurs on 40. most are like the following
> 
> MSI (s) (40:08) [11:57:25:973]: Package to be registered: 
> 'python-3.4.0rc1.amd64.msi'
> MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: Error 3: -2147287038
> MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: AdminProperties 3: 
> -2147287038
> 
> Here is the one for the boxed message:
> 
> Action 11:57:26: RemovePip.
> Action start 11:57:26: RemovePip.
> MSI (s) (40:0C) [11:57:26:426]: Note: 1: 1721 2: RemovePip 3: 
> C:\Programs\Python34\python.exe 4: -m ensurepip._uninstall
> MSI (s) (40:0C) [11:57:26:426]: Note: 1: 2262 2: Error 3: -2147287038
> Error 1721. There is a problem with this Windows Installer package. A 
> program required for this install to complete could not be run. Contact 
> your support personnel or package vendor. Action: RemovePip, location: 
> C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall
> MSI (s) (40:0C) [11:57:28:874]: Note: 1: 2262 2: Error 3: -2147287038
> MSI (s) (40:0C) [11:57:28:874]: Product: Python 3.4.0b2 (64-bit) -- 
> Error 1721. There is a problem with this Windows Installer package. A 
> program required for this install to complete could not be run. Contact 
> your support personnel or package vendor. Action: RemovePip, location: 
> C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall
> 
> MSI (c) (98:EC) [11:57:30:204]: PROPERTY CHANGE: Deleting SECONDSEQUENCE 
> property. Its current value is '1'.
> Action ended 11:57:30: ExecuteAction. Return value 3.
> MSI (c) (98:EC) [11:57:30:204]: Doing action: FatalError
> A
> 
> Can you make anything of these?

Interesting. I just had problems trying to install the 32-bit rc1
(see thread in py-dev; I think it's now "solved"). 

Here's what Windows Event Viewer said:

'''
Product: Python 3.4.0b3 -- Error 1721. There is a problem with
this Windows Installer package. A program required for this
install to complete could not be run. Contact your support
personnel or package vendor. Action: RemovePip, location:
C:\Python34\python.exe, command: -m ensurepip._uninstall 
'''

Not sure why the installers are complaining about 3.4.0b3...?

Pip seems to be figuring into these glitches, somehow...? 

(Note that both Terry and I are longtime Windows users, so likely
we're both using our own procedures which *have* worked for
years.)

Bob Hanson

-- 
Confucius say, "Never, ever, make apps dependent on the Windows
Registry."

[toc] | [prev] | [next] | [standalone]

#66121

On 2/12/2014 2:42 PM, Bob Hanson wrote:
> [32-bit Windows XP-SP2]
>
> On Tue, 11 Feb 2014 12:11:49 -0500, Terry Reedy wrote:
>
>> [problems installing rc1]
>>
>> On 2/11/2014 10:42 AM, Duncan Booth wrote:
>>
>>> Does it put any useful messages in logfile.txt?
>>
>> 'error' occurs on 40. most are like the following
>>
>> MSI (s) (40:08) [11:57:25:973]: Package to be registered:
>> 'python-3.4.0rc1.amd64.msi'
>> MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: Error 3: -2147287038
>> MSI (s) (40:08) [11:57:25:973]: Note: 1: 2262 2: AdminProperties 3:
>> -2147287038
>>
>> Here is the one for the boxed message:
>>
>> Action 11:57:26: RemovePip.
>> Action start 11:57:26: RemovePip.
>> MSI (s) (40:0C) [11:57:26:426]: Note: 1: 1721 2: RemovePip 3:
>> C:\Programs\Python34\python.exe 4: -m ensurepip._uninstall
>> MSI (s) (40:0C) [11:57:26:426]: Note: 1: 2262 2: Error 3: -2147287038
>> Error 1721. There is a problem with this Windows Installer package. A
>> program required for this install to complete could not be run. Contact
>> your support personnel or package vendor. Action: RemovePip, location:
>> C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall
>> MSI (s) (40:0C) [11:57:28:874]: Note: 1: 2262 2: Error 3: -2147287038
>> MSI (s) (40:0C) [11:57:28:874]: Product: Python 3.4.0b2 (64-bit) --
>> Error 1721. There is a problem with this Windows Installer package. A
>> program required for this install to complete could not be run. Contact
>> your support personnel or package vendor. Action: RemovePip, location:
>> C:\Programs\Python34\python.exe, command: -m ensurepip._uninstall
>>
>> MSI (c) (98:EC) [11:57:30:204]: PROPERTY CHANGE: Deleting SECONDSEQUENCE
>> property. Its current value is '1'.
>> Action ended 11:57:30: ExecuteAction. Return value 3.
>> MSI (c) (98:EC) [11:57:30:204]: Doing action: FatalError
>> A
>>
>> Can you make anything of these?
>
> Interesting. I just had problems trying to install the 32-bit rc1
> (see thread in py-dev; I think it's now "solved").
>
> Here's what Windows Event Viewer said:
>
> '''
> Product: Python 3.4.0b3 -- Error 1721. There is a problem with
> this Windows Installer package. A program required for this
> install to complete could not be run. Contact your support
> personnel or package vendor. Action: RemovePip, location:
> C:\Python34\python.exe, command: -m ensurepip._uninstall
> '''
>
> Not sure why the installers are complaining about 3.4.0b3...?
>
> Pip seems to be figuring into these glitches, somehow...?
>
> (Note that both Terry and I are longtime Windows users, so likely
> we're both using our own procedures which *have* worked for
> years.)

In my case, the problem appears to be that 3.4.0b3 did not completely 
uninstall and overwrite .0b2.  Control Panel / Programs and Features 
(new name for Add/Remove) had entries for both .0b2 and .0b3, which it 
should not have. Trying to uninstall .0b2 gave same message. So I 
re-downloaded the .0b2 file from python.org/ftp/python/3.4.0, repaired 
.0b2, and then uninstalled it. The 64 bit .0c1 then seems to have 
installed Ok.

-- 
Terry Jan Reedy

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web