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

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

Both Python 2.5.2 and 2.7.2 flop the same way under Win 7

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

Contents

  Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-17 08:55 -0800
    Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 ray <ray040123@gmail.com> - 2011-11-18 01:37 +0800
    Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "spartan.the" <spartan.the@gmail.com> - 2011-11-17 09:37 -0800
    Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 John Gordon <gordon@panix.com> - 2011-11-17 17:39 +0000
      Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-17 12:22 -0800
      Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-17 12:31 -0800
        Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Chris Angelico <rosuav@gmail.com> - 2011-11-18 07:43 +1100
          Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Alan Meyer <ameyer2@yahoo.com> - 2011-11-21 17:43 -0500
        Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 MRAB <python@mrabarnett.plus.com> - 2011-11-17 20:59 +0000
          Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-17 16:00 -0800
        Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "spartan.the" <spartan.the@gmail.com> - 2011-11-17 12:46 -0800
          Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-17 15:54 -0800
            Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "Martin P. Hellwig" <martin.hellwig@gmail.com> - 2011-11-18 01:55 +0000
        Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Dave Angel <d@davea.name> - 2011-11-17 22:59 -0500
          Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-17 20:21 -0800
            Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Benjamin Kaplan <benjamin.kaplan@case.edu> - 2011-11-18 00:25 -0500
              Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-18 09:59 -0800
                Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 alex23 <wuwei23@gmail.com> - 2011-11-20 21:04 -0800
            Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 alex23 <wuwei23@gmail.com> - 2011-11-17 22:06 -0800
          Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Tony the Tiger <tony@tiger.invalid> - 2011-11-18 15:46 -0600
    Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2011-11-17 18:42 +0000
    Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Terry Reedy <tjreedy@udel.edu> - 2011-11-17 17:12 -0500
      Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-17 16:03 -0800
        Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2011-11-18 00:24 +0000
          Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-17 20:33 -0800
            Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Neil Cerutti <neilc@norwich.edu> - 2011-11-18 13:11 +0000
              Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-18 07:29 -0800
                Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 MRAB <python@mrabarnett.plus.com> - 2011-11-18 17:12 +0000
                  Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 rusi <rustompmody@gmail.com> - 2011-11-18 09:19 -0800
                    Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-18 09:48 -0800
                  Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-18 09:45 -0800
                    Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2011-11-18 17:17 -0800
                Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2011-11-18 10:04 -0800
        Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Terry Reedy <tjreedy@udel.edu> - 2011-11-18 02:35 -0500
          Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-18 09:57 -0800
    Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 alex23 <wuwei23@gmail.com> - 2011-11-17 19:04 -0800
      Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-17 20:34 -0800
        Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Stephen Hansen <me+list/python@ixokai.io> - 2011-11-18 14:31 -0800
          Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 alex23 <wuwei23@gmail.com> - 2011-11-20 21:09 -0800
    Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2011-11-17 20:34 -0800
      Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-18 07:54 -0800
      Re: Both Python 2.5.2 and 2.7.2 flop the same way under Win 7 "W. eWatson" <wolftracks@invalid.com> - 2011-11-18 07:57 -0800

Page 1 of 3  [1] 2 3  Next page →

#15823 — Both Python 2.5.2 and 2.7.2 flop the same way under Win 7

Months ago 2.5.2 stopped functioning on my Win7 PC, so a few days ago I 
uninstalled and installed. Same problem. If one right-clicks on a py 
file, IDLE is not shown in the menu as Edit with IDLE. After playing 
with matters I gave up, and uninstalled 2.5.2 and turned to 2.7.2. Same 
results.

If I look at a 2.4 install on my laptop, I get the desired reference to 
Edit with IDLE.

My guess is that Win 7 is behind this. If so, it's good-bye Python.

Comments?

[toc] | [next] | [standalone]

#15825

On Friday, November 18, 2011 12:55 AM, W. eWatson wrote:
> Months ago 2.5.2 stopped functioning on my Win7 PC, so a few days ago 
> I uninstalled and installed. Same problem. If one right-clicks on a py 
> file, IDLE is not shown in the menu as Edit with IDLE. After playing 
> with matters I gave up, and uninstalled 2.5.2 and turned to 2.7.2. 
> Same results.
>
> If I look at a 2.4 install on my laptop, I get the desired reference 
> to Edit with IDLE.
>
> My guess is that Win 7 is behind this. If so, it's good-bye Python.
>
> Comments?
Why not good-bye Windows ? Actually you may want to try Vim, or gVim in 
Windows. I think the people who use IDLE is with really good patient.

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

#15826

On 17 Nov, 18:55, "W. eWatson" <wolftra...@invalid.com> wrote:
> Months ago 2.5.2 stopped functioning on my Win7 PC, so a few days ago I
> uninstalled and installed. Same problem. If one right-clicks on a py
> file, IDLE is not shown in the menu as Edit with IDLE. After playing
> with matters I gave up, and uninstalled 2.5.2 and turned to 2.7.2. Same
> results.
>
> If I look at a 2.4 install on my laptop, I get the desired reference to
> Edit with IDLE.
>
> My guess is that Win 7 is behind this. If so, it's good-bye Python.
>
> Comments?

I prefer "fail fast" approach too.

If right-click not working on Win7 is your reason to say good bye to
Python then better you do so.

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

#15827

In <ja3eae$rr$1@dont-email.me> "W. eWatson" <wolftracks@invalid.com> writes:

> Months ago 2.5.2 stopped functioning on my Win7 PC, so a few days ago I 
> uninstalled and installed. Same problem. If one right-clicks on a py 
> file, IDLE is not shown in the menu as Edit with IDLE. After playing 
> with matters I gave up, and uninstalled 2.5.2 and turned to 2.7.2. Same 
> results.

I'm not sure I'd describe the lack of IDLE in a context menu as
"python not functioning".

> If I look at a 2.4 install on my laptop, I get the desired reference to 
> Edit with IDLE.

> My guess is that Win 7 is behind this. If so, it's good-bye Python.

It was working originally, right?  So the problem can't really just be
Win 7.

Can you add IDLE manually to the associated applications list?

-- 
John Gordon                   A is for Amy, who fell down the stairs
gordon@panix.com              B is for Basil, assaulted by bears
                                -- Edward Gorey, "The Gashlycrumb Tinies"

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

#15830

On 11/17/2011 9:39 AM, John Gordon wrote:
> In<ja3eae$rr$1@dont-email.me>  "W. eWatson"<wolftracks@invalid.com>  writes:
>
>> Months ago 2.5.2 stopped functioning on my Win7 PC, so a few days ago I
>> uninstalled and installed. Same problem. If one right-clicks on a py
>> file, IDLE is not shown in the menu as Edit with IDLE. After playing
>> with matters I gave up, and uninstalled 2.5.2 and turned to 2.7.2. Same
>> results.
>
> I'm not sure I'd describe the lack of IDLE in a context menu as
> "python not functioning".
>
>> If I look at a 2.4 install on my laptop, I get the desired reference to
>> Edit with IDLE.
>
>> My guess is that Win 7 is behind this. If so, it's good-bye Python.
>
> It was working originally, right?  So the problem can't really just be
> Win 7.
>
> Can you add IDLE manually to the associated applications list?
>
Not successfully. I tried it and pointed to idle.pyw. It gave a Invalid 
Win32 app.

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

#15831

On 11/17/2011 9:39 AM, John Gordon wrote:
> In<ja3eae$rr$1@dont-email.me>  "W. eWatson"<wolftracks@invalid.com>  writes:
>
>> Months ago 2.5.2 stopped functioning on my Win7 PC, so a few days ago I
>> uninstalled and installed. Same problem. If one right-clicks on a py
>> file, IDLE is not shown in the menu as Edit with IDLE. After playing
>> with matters I gave up, and uninstalled 2.5.2 and turned to 2.7.2. Same
>> results.
>
> I'm not sure I'd describe the lack of IDLE in a context menu as
> "python not functioning".
Well, yes, and I can run it from the command line.
>
>> If I look at a 2.4 install on my laptop, I get the desired reference to
>> Edit with IDLE.
>
>> My guess is that Win 7 is behind this. If so, it's good-bye Python.
This has been a nagging problem for far too long. I see no reason why a 
simple install should make such a difference with the way I get to IDLE. 
Maybe few people here like IDLE, but for my minimal needs, it's just fine.

>
> It was working originally, right?  So the problem can't really just be
> Win 7.
I installed it about April 2010, and it worked for months. I then 
stopped using it until around July 2011. It no longer worked in the IDLE 
sense.

Who really knows?

>
> Can you add IDLE manually to the associated applications list?
>
Tried that by sending it directly to idle.pyw, but then trying to get 
there through the Edit with menu caused a "invalid Win32 app."

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

#15832

On Fri, Nov 18, 2011 at 7:31 AM, W. eWatson <wolftracks@invalid.com> wrote:
> I installed it [Windows 7] about April 2010, and it worked for months. I then stopped
> using it until around July 2011. It no longer worked in the IDLE sense.
>

Microsoft have broken things in many Windowses, and it's often hard to
figure out whether the fault is with the Windows version or with the
application. MS several times went to ridiculous effort to try to
ensure that broken programs that ran under version X would still run
under version Y, to the extent of being bug-for-bug compatible.

If you're having issues, grab a spare computer, throw Linux on it (I
recommend Ubuntu or Debian, others will have other preferred distros),
and see if the issues remain. Or if you're having trouble with the
GUI, try things from the command line (Windows's command interpreter
is pretty weak compared to bash, but it's plenty powerful enough).

ChrisA

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

#16052

On 11/17/2011 3:43 PM, Chris Angelico wrote:
> ...
> If you're having issues, grab a spare computer, throw Linux on it (I
> recommend Ubuntu or Debian, others will have other preferred distros),
> and see if the issues remain. Or if you're having trouble with the
> GUI, try things from the command line (Windows's command interpreter
> is pretty weak compared to bash, but it's plenty powerful enough).
>
> ChrisA

If the OP is having trouble with this issue, and if he can't make 
Windows work here, I suspect that he'll get into trouble trying to 
install and test with Linux.

However if he did want to try it, and assuming he's got 8GB or so of 
extra space, one easy way to test with Linux is to install VirtualBox, 
then install Linux under that.  I've done that a half dozen times 
without hiccups.  That way he doesn't need a second machine and doesn't 
need to repartition or toss his old OS.

     Alan

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

#15834

On 17/11/2011 20:31, W. eWatson wrote:
> On 11/17/2011 9:39 AM, John Gordon wrote:
>> In<ja3eae$rr$1@dont-email.me> "W. eWatson"<wolftracks@invalid.com>
>> writes:
>>
>>> Months ago 2.5.2 stopped functioning on my Win7 PC, so a few days ago I
>>> uninstalled and installed. Same problem. If one right-clicks on a py
>>> file, IDLE is not shown in the menu as Edit with IDLE. After playing
>>> with matters I gave up, and uninstalled 2.5.2 and turned to 2.7.2. Same
>>> results.
>>
>> I'm not sure I'd describe the lack of IDLE in a context menu as
>> "python not functioning".
> Well, yes, and I can run it from the command line.
>>
>>> If I look at a 2.4 install on my laptop, I get the desired reference to
>>> Edit with IDLE.
>>
>>> My guess is that Win 7 is behind this. If so, it's good-bye Python.
> This has been a nagging problem for far too long. I see no reason why a
> simple install should make such a difference with the way I get to IDLE.
> Maybe few people here like IDLE, but for my minimal needs, it's just fine.
>
>>
>> It was working originally, right? So the problem can't really just be
>> Win 7.
> I installed it about April 2010, and it worked for months. I then
> stopped using it until around July 2011. It no longer worked in the IDLE
> sense.
>
> Who really knows?
>
>>
>> Can you add IDLE manually to the associated applications list?
>>
> Tried that by sending it directly to idle.pyw, but then trying to get
> there through the Edit with menu caused a "invalid Win32 app."

Are you trying to associate .pyw with idle.pyw instead of with
pythonw.exe?

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

#15840

On 11/17/2011 12:59 PM, MRAB wrote:
> On 17/11/2011 20:31, W. eWatson wrote:
>> On 11/17/2011 9:39 AM, John Gordon wrote:
>>> In<ja3eae$rr$1@dont-email.me> "W. eWatson"<wolftracks@invalid.com>
>>> writes:
>>>
>>>> Months ago 2.5.2 stopped functioning on my Win7 PC, so a few days ago I
>>>> uninstalled and installed. Same problem. If one right-clicks on a py
>>>> file, IDLE is not shown in the menu as Edit with IDLE. After playing
>>>> with matters I gave up, and uninstalled 2.5.2 and turned to 2.7.2. Same
>>>> results.
>>>
>>> I'm not sure I'd describe the lack of IDLE in a context menu as
>>> "python not functioning".
>> Well, yes, and I can run it from the command line.
>>>
>>>> If I look at a 2.4 install on my laptop, I get the desired reference to
>>>> Edit with IDLE.
>>>
>>>> My guess is that Win 7 is behind this. If so, it's good-bye Python.
>> This has been a nagging problem for far too long. I see no reason why a
>> simple install should make such a difference with the way I get to IDLE.
>> Maybe few people here like IDLE, but for my minimal needs, it's just
>> fine.
>>
>>>
>>> It was working originally, right? So the problem can't really just be
>>> Win 7.
>> I installed it about April 2010, and it worked for months. I then
>> stopped using it until around July 2011. It no longer worked in the IDLE
>> sense.
>>
>> Who really knows?
>>
>>>
>>> Can you add IDLE manually to the associated applications list?
>>>
>> Tried that by sending it directly to idle.pyw, but then trying to get
>> there through the Edit with menu caused a "invalid Win32 app."
>
> Are you trying to associate .pyw with idle.pyw instead of with
> pythonw.exe?
What does pythonw.exe do for me? I would think all associations would be 
correct after an install.

The single thing I do not understand is why in my latest install of 
2.5.2 and 2.7.2 (2.5.2 was uninstalled before going to 2.7.2) on Win7 
that why a right-click on a py file does not show as a choice is "Edit 
with IDLE", as it does on my XP PC and my 2010 install of 2.5.2 on this 
Win 7 PC. To me that signals that something is wrong.

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

#15835

On Nov 17, 10:31 pm, "W. eWatson" <wolftra...@invalid.com> wrote:
> On 11/17/2011 9:39 AM, John Gordon wrote:> In<ja3eae$r...@dont-email.me>  "W. eWatson"<wolftra...@invalid.com>  writes:
>
> >> Months ago 2.5.2 stopped functioning on my Win7 PC, so a few days ago I
> >> uninstalled and installed. Same problem. If one right-clicks on a py
> >> file, IDLE is not shown in the menu as Edit with IDLE. After playing
> >> with matters I gave up, and uninstalled 2.5.2 and turned to 2.7.2. Same
> >> results.
>
> > I'm not sure I'd describe the lack of IDLE in a context menu as
> > "python not functioning".
>
> Well, yes, and I can run it from the command line.
>
> >> If I look at a 2.4 install on my laptop, I get the desired reference to
> >> Edit with IDLE.
>
> >> My guess is that Win 7 is behind this. If so, it's good-bye Python.
>
> This has been a nagging problem for far too long. I see no reason why a
> simple install should make such a difference with the way I get to IDLE.
> Maybe few people here like IDLE, but for my minimal needs, it's just fine.
>
>
>
> > It was working originally, right?  So the problem can't really just be
> > Win 7.
>
> I installed it about April 2010, and it worked for months. I then
> stopped using it until around July 2011. It no longer worked in the IDLE
> sense.
>
> Who really knows?
>
>
>
> > Can you add IDLE manually to the associated applications list?
>
> Tried that by sending it directly to idle.pyw, but then trying to get
> there through the Edit with menu caused a "invalid Win32 app."

idle.pyw is not executable in Windows, but you can right-click it,
open, browse to pythonw.exe. Then it should work.

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

#15839

On 11/17/2011 12:46 PM, spartan.the wrote:
> On Nov 17, 10:31 pm, "W. eWatson"<wolftra...@invalid.com>  wrote:
>> On 11/17/2011 9:39 AM, John Gordon wrote:>  In<ja3eae$r...@dont-email.me>    "W. eWatson"<wolftra...@invalid.com>    writes:
>>
>>>> Months ago 2.5.2 stopped functioning on my Win7 PC, so a few days ago I
>>>> uninstalled and installed. Same problem. If one right-clicks on a py
>>>> file, IDLE is not shown in the menu as Edit with IDLE. After playing
>>>> with matters I gave up, and uninstalled 2.5.2 and turned to 2.7.2. Same
>>>> results.
>>
>>> I'm not sure I'd describe the lack of IDLE in a context menu as
>>> "python not functioning".
>>
>> Well, yes, and I can run it from the command line.
>>
>>>> If I look at a 2.4 install on my laptop, I get the desired reference to
>>>> Edit with IDLE.
>>
>>>> My guess is that Win 7 is behind this. If so, it's good-bye Python.
>>
>> This has been a nagging problem for far too long. I see no reason why a
>> simple install should make such a difference with the way I get to IDLE.
>> Maybe few people here like IDLE, but for my minimal needs, it's just fine.
>>
>>
>>
>>> It was working originally, right?  So the problem can't really just be
>>> Win 7.
>>
>> I installed it about April 2010, and it worked for months. I then
>> stopped using it until around July 2011. It no longer worked in the IDLE
>> sense.
>>
>> Who really knows?
>>
>>
>>
>>> Can you add IDLE manually to the associated applications list?
>>
>> Tried that by sending it directly to idle.pyw, but then trying to get
>> there through the Edit with menu caused a "invalid Win32 app."
>
> idle.pyw is not executable in Windows, but you can right-click it,
> open, browse to pythonw.exe. Then it should work.

right-click on junk.py gives me a menu. I select Open with, and ... 
hmmm, whoops, in the latest install, 2.7.2, I did not give it access to 
idle.pyw.

My mistake above. I was talking about the previous 2.5.2 of install in 
Win7. Where I'm at is 2.7.2 now. However, I still find in very odd there 
is no Edit with IDLE when I right-click on junk.py. That's the way it 
worked on 2.5.2 on my XP and earlier, 2010, on Win7. Downright frustrating.

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

#15845

On 17/11/2011 23:54, W. eWatson wrote:
<cut>
> My mistake above. I was talking about the previous 2.5.2 of install in
> Win7. Where I'm at is 2.7.2 now. However, I still find in very odd there
> is no Edit with IDLE when I right-click on junk.py. That's the way it
> worked on 2.5.2 on my XP and earlier, 2010, on Win7. Downright frustrating.
>

Well if I was still a windows administrator and you would be one of my 
users, I would first make sure that your profile or windows installation 
is not pooped as it definitively smells like that.

After being reassured that this is not the case I would then search the 
interwebs for something like "extending right click context menu".

Probably hitting something like this:

http://answers.microsoft.com/en-us/windows/forum/windows_7-desktop/how-can-i-customize-right-click-mouse-context-menu/5ea7104f-2213-41b9-9933-83f25da086d1

And after that searching where this 'idle' you speak of is actually 
located, probably finding something like this:

http://stackoverflow.com/questions/118260/how-to-start-idle-python-editor-without-using-the-shortcut-on-windows-vista

Then it rest me to combine them both, after promising myself not to 
install one version of a particular program 'for all users' and then 
'updating' for 'only me' as this can screw up the default settings quite 
badly.

But hey I haven't been a win admin since I switched over to FreeBSD 
years and years ago. I find it immensely reassuring that the problems I 
encounter on my systems are all my fault, well actually that is just the 
same as with windows, just less obvious there.

Luckily I am no longer an administrator either as I couldn't stand it 
anymore when users spill their frustrations, although perfectly 
understandable, unto those who are actually willing to help.

Something to do with attitude or so, speaking if which, I do apologize 
for my own attitude, but given the choice of just ignoring you or lacing 
my post with patronization I though that the latter one was the least 
bad of them two.

-- 
mph

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

#15856

On 11/17/2011 03:31 PM, W. eWatson wrote:
> On 11/17/2011 9:39 AM, John Gordon wrote:
> <SNIP>
>>
>> Can you add IDLE manually to the associated applications list?
>>
> Tried that by sending it directly to idle.pyw, but then trying to get 
> there through the Edit with menu caused a "invalid Win32 app."

You've been told repeatedly that building an association to idle.pyw is 
useless.  It must be to something Windows understands, such as .exe, or 
.bat (or several other extensions, as I said in an earlier message)   So 
why waste our time telling us yet again that it doesn't work?



-- 

DaveA

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

#15857

On 11/17/2011 7:59 PM, Dave Angel wrote:
> On 11/17/2011 03:31 PM, W. eWatson wrote:
>> On 11/17/2011 9:39 AM, John Gordon wrote:
>> <SNIP>
>>>
>>> Can you add IDLE manually to the associated applications list?
>>>
>> Tried that by sending it directly to idle.pyw, but then trying to get
>> there through the Edit with menu caused a "invalid Win32 app."
>
> You've been told repeatedly that building an association to idle.pyw is
> useless. It must be to something Windows understands, such as .exe, or
> .bat (or several other extensions, as I said in an earlier message) So
> why waste our time telling us yet again that it doesn't work?
>
>
>
Because some  people think that's a solution, and ask. It's not. It 
leads to an error message.

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

#15868

On Thu, Nov 17, 2011 at 11:21 PM, W. eWatson <wolftracks@invalid.com> wrote:
>
> On 11/17/2011 7:59 PM, Dave Angel wrote:
>>
>> On 11/17/2011 03:31 PM, W. eWatson wrote:
>>>
>>> On 11/17/2011 9:39 AM, John Gordon wrote:
>>> <SNIP>
>>>>
>>>> Can you add IDLE manually to the associated applications list?
>>>>
>>> Tried that by sending it directly to idle.pyw, but then trying to get
>>> there through the Edit with menu caused a "invalid Win32 app."
>>
>> You've been told repeatedly that building an association to idle.pyw is
>> useless. It must be to something Windows understands, such as .exe, or
>> .bat (or several other extensions, as I said in an earlier message) So
>> why waste our time telling us yet again that it doesn't work?
>>
>>
>>
> Because some  people think that's a solution, and ask. It's not. It leads to an error message.


Checking my Python install, there should be an idle.bat file in there
too. Have you tried that?

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

#15911

On 11/17/2011 9:25 PM, Benjamin Kaplan wrote:
> On Thu, Nov 17, 2011 at 11:21 PM, W. eWatson<wolftracks@invalid.com>  wrote:
>>
>> On 11/17/2011 7:59 PM, Dave Angel wrote:
>>>
>>> On 11/17/2011 03:31 PM, W. eWatson wrote:
>>>>
>>>> On 11/17/2011 9:39 AM, John Gordon wrote:
>>>> <SNIP>
>>>>>
>>>>> Can you add IDLE manually to the associated applications list?
>>>>>
>>>> Tried that by sending it directly to idle.pyw, but then trying to get
>>>> there through the Edit with menu caused a "invalid Win32 app."
>>>
>>> You've been told repeatedly that building an association to idle.pyw is
>>> useless. It must be to something Windows understands, such as .exe, or
>>> .bat (or several other extensions, as I said in an earlier message) So
>>> why waste our time telling us yet again that it doesn't work?
>>>
>>>
>>>
>> Because some  people think that's a solution, and ask. It's not. It leads to an error message.
>
>
> Checking my Python install, there should be an idle.bat file in there
> too. Have you tried that?
Yes. I tried running it. Got nowhere.

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

#15980

On Nov 19, 3:59 am, "W. eWatson" <wolftra...@invalid.com> wrote:
> Yes. I tried running it. Got nowhere.

Did you run it from the shell? Did it spit out any errors?

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

#15872

On Nov 18, 2:21 pm, "W. eWatson" <wolftra...@invalid.com> wrote:
> Because some  people think that's a solution, and ask. It's not. It
> leads to an error message.

No, people are saying "manually add IDLE _the correct way that Windows
can recognise_", not recommending you stuff random .pyw files into the
context menu and hope they work.

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

#15918

On Thu, 17 Nov 2011 22:59:17 -0500, Dave Angel wrote:

[...]
> extensions, as I said in an earlier message)   So why waste our time
> telling us yet again that it doesn't work?

A Saturday night, 11 p.m. A man, drunk as a skunk, was crawling around on 
all four under a street light. This helpful fellow walks up to him and 
asks, "Have you lost something?" "Yeah, I l-lost my keys, s-so I can't 
get in." "Okay, I'll help you look," said the helpful fellow. Both of 
them were now crawling around on all four under the street light.
After a while, the helpful fellow asks "Are you sure you lost them here?" 
"No," said the drunk, "it was o-over there. B-but it's brighter over 
here."

Perhaps it's something like that...?


 /Grrr
-- 
          ___                  ___
 (\_--_/)  | _ ._    _|_|_  _   |o _  _ ._
 ( 9  9 )  |(_)| |\/  |_| |(/_  ||(_|(/_|
 stripes are forever - as overripe ferrets

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

Page 1 of 3  [1] 2 3  Next page →

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

csiph-web