pythonw crashes under one windows platform (easy-everything)

[angelpeream]

BPO	764049
Nosy	@tim-one, @rhettinger

^{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 = None
closed_at = <Date 2003-07-25.17:27:41.000>
created_at = <Date 2003-07-01.16:47:19.000>
labels = ['OS-windows']
title = 'pythonw crashes under one windows platform (easy-everything)'
updated_at = <Date 2003-07-25.17:27:41.000>
user = 'https://bugs.python.org/angelpeream'

bugs.python.org fields:

activity = <Date 2003-07-25.17:27:41.000>
actor = 'angelpeream'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2003-07-01.16:47:19.000>
creator = 'angelpeream'
dependencies = []
files = []
hgrepos = []
issue_num = 764049
keywords = []
message_count = 4.0
messages = ['16773', '16774', '16775', '16776']
nosy_count = 3.0
nosy_names = ['tim.peters', 'rhettinger', 'angelpeream']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue764049'
versions = []

[angelpeream]

pythonw (Python 2.3b2 (#43, Jun 29 2003, 16:43:04))
crashes (performs an invalid operation) under some
special windows platform (easy-everything internet-cafe
PCs). Previous versions showed no problem.

Not surely a bug, but disencourages trying the language.

[tim-one]

Logged In: YES
user_id=31435

Unassigned. If someone with access to such a platform
doesn't dig into this, it appears hopeless.

[rhettinger]

Logged In: YES
user_id=80475

Do you have any idea of where it crashes? Can you dig in to
it and find out which verison in CVS is the first to not run?
Otherwise, it is like Tim says, the bug report is equilavent of
saying the something appears wrong on the dark side of the
moon.

[angelpeream]

Logged In: YES
user_id=606911

I couldnt dig in it. That platform has proved not very...
cooperative, but it does'nt happen in 2.3c2 anymore, so,
whatever it was, got fixed.