Problems with the msi installer - python-3.0a1.msi

[vbr]

BPO	1110
Nosy	@loewis, @tiran
Superseder	bpo-1403: py_compile and compileall need unit tests

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/loewis'
closed_at = <Date 2007-11-08.14:07:23.399>
created_at = <Date 2007-09-05.18:20:07.560>
labels = ['OS-windows']
title = 'Problems with the msi installer - python-3.0a1.msi'
updated_at = <Date 2007-12-07.20:53:02.365>
user = 'https://bugs.python.org/vbr'

bugs.python.org fields:

activity = <Date 2007-12-07.20:53:02.365>
actor = 'vbr'
assignee = 'loewis'
closed = True
closed_date = <Date 2007-11-08.14:07:23.399>
closer = 'christian.heimes'
components = ['Windows']
creation = <Date 2007-09-05.18:20:07.560>
creator = 'vbr'
dependencies = []
files = []
hgrepos = []
issue_num = 1110
keywords = []
message_count = 5.0
messages = ['55665', '55666', '55669', '57246', '58282']
nosy_count = 3.0
nosy_names = ['loewis', 'christian.heimes', 'vbr']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = '1403'
type = None
url = 'https://bugs.python.org/issue1110'
versions = ['Python 3.0']

[vbr]

I encountered problems installing python 3.0 alpha 1 from the MSI
installer supplied on the python download page (python-3.0a1.msi).
If the advanced option of the installer ("compile .py files to bytecode
after installation") is checked - the following message is shown
"There is a problem with this Windows installer package. A program run
as part of the setup did not finish as expected ..."
If I don't choose the option to compile files, the installation
finishes without any visible errors.

The result is in both cases the same however. After calling python.exe 
it shows the version info etc. in the interactive prompt, but it 
doesn't "respond" in any way.
e.g.
>>> 1+1
object  : RuntimeError('lost sys.stdout',)
type    : RuntimeError
refcount: 4
address : 00A65BD0
lost sys.stderr
>>> 

Running of any .py file doesn't work either.

My system is Win XPh SP2 Czech (the same on Win XPp SP2 Czech).

Could possibly the Czech windows version/ language setting/ locale/
timezone or whatever be the problem (as there were some problems
reported with the manual compilation on German or Polish Winsows-
systems)?

Or am I missing something trivial?

Thanks,
Vlastimil Brom

[loewis]

There are really two issues here; it is usually better to report them
separately, so they can be analyzed, fixed, and closed separately:
a) the compileall script apparently fails (not surprisingly so, I never
tested it for 3.0), and
b) Python does not work on your version of Windows.

Please confirm that you use the Python console, not IDLE.

As for issue b), yes, that's possibly a locale-related problem. How is
"Program Files" called in your installation? What target directory did
you set for Python?

[vbr]

The path to the python executable on my system is:
"C:\Python30\python.exe"

The path to Program Files is "C:\Program Files", but it doesn't matter
in that case, I guess.

And yes, I use the console window (i.e. the cmd window in Windows) -
the IDLE doesn't run either, as all other .py files (using python 3.0).

[tiran]

I've validated a) and fixed b) two weeks ago. I'm closing this bug. It
doesn't contain any additional problems for the bug.

I expect the next alpha of Python 3.0 in about two weeks. Please test
the next version, would you? The problems with your localization of
Windows should be fixed as long as you don't install Python into a
directory with non ASCII letters.

[vbr]

I just installed python-3.0a2 and it works fine for me (Win XPh SP2
Czech; python3 directory C:\Python30). Sofar I haven't found any
problems other than those mentioned in the release notes.
Thank you very much for fixing this!