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


Groups > comp.lang.python > #27283

Re: Crashes always on Windows 7

From Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject Re: Crashes always on Windows 7
Date 2012-08-18 01:25 -0400
Organization > Bestiaria Support Staff <
References <4c344999-81c3-4c46-a6a8-eb5dc2fcc988@googlegroups.com> <b3cc7f5a-a413-45cf-b601-403b2ec6617f@googlegroups.com>
Newsgroups comp.lang.python
Message-ID <mailman.3441.1345267531.4697.python-list@python.org> (permalink)

Show all headers | View raw


On Fri, 17 Aug 2012 20:09:12 -0700 (PDT), zmagic11@gmail.com declaimed
the following in gmane.comp.python.general:

> 
> Hi Hi, sorry for the confusion. Yes, I meant ActiveState ActivePython. It worked fine for a few hours and now every time I open up the IDLE Shell, it opens fine. Then when I try to open a previously made file, the shell immediately closes and nothing else happens. When I enter Python in the command line, I get the ActivePython information. 

	Which still doesn't tell us everything...

	HOW are you trying "to open a previously made file"? WHAT do you
even /mean/ by "open"?

	Gazing into a crystal ball, while on the verge of a drunken stupor
compounded by lack of sleep..

	I see you <double-clicking> on a .py file icon.

	Double-clicking a .py file, on a PROPER Python install, will attempt
to RUN the script. This commonly results in a Windows "command prompt"
(console window) flashing onto the screen (stdin and stdout are hooked
to that console). When the script exits (for whatever reason -- likely
because it has no data to process), the console window will go away.

	To edit the file, you'll need to open whatever editing program you
favor, and use it's "file/open..." menu to find the file to be edited
(or, in a fully aware system, drag the .py file icon /to/ the editor
window).

	Note that IDLE itself is a Python script, so you can not have the
"open" action of double click on a .py file assigned to run IDLE as an
editor -- because double clicking on an IDLE.py would try to open IDLE
for editing /using itself/. 

	On my WinXP system, <right-click> on a .py file reveals an "edit"
command option -- which opens PythonWin with the file in an edit window.
I can also use the "send to" list to send the file to SciTE for editing
if I prefer to use that one.
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
        wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Crashes always on Windows 7 zmagic11@gmail.com - 2012-08-17 06:38 -0700
  Re: Crashes always on Windows 7 Dave Angel <d@davea.name> - 2012-08-17 10:54 -0400
  Re: Crashes always on Windows 7 Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-08-17 15:07 -0400
  Re: Crashes always on Windows 7 zmagic11@gmail.com - 2012-08-17 20:09 -0700
    Re: Crashes always on Windows 7 Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-08-18 01:25 -0400
    Re: Crashes always on Windows 7 Terry Reedy <tjreedy@udel.edu> - 2012-08-18 02:26 -0400
  Re: Crashes always on Windows 7 zmagic11@gmail.com - 2012-08-17 23:18 -0700
    Re: Crashes always on Windows 7 Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-08-18 13:27 -0400
    Re: Crashes always on Windows 7 Terry Reedy <tjreedy@udel.edu> - 2012-08-18 13:32 -0400

csiph-web