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


Groups > comp.lang.python > #77071

Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?

Path csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path <zachary.ware@gmail.com>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.003
X-Spam-Evidence '*H*': 0.99; '*S*': 0.00; 'subject:IDLE': 0.04; 'tries': 0.07; 'string': 0.09; 'escape': 0.09; 'formatting': 0.09; 'literal': 0.09; 'windows': 0.15; "'from": 0.16; '(sorry,': 0.16; '170,': 0.16; 'backslash': 0.16; 'idle.': 0.16; 'literal.': 0.16; 'reedy': 0.16; 'simplest': 0.16; 'string).': 0.16; 'subject: \n ': 0.16; 'syntaxerror:': 0.16; 'sender:addr:gmail.com': 0.17; 'wrote:': 0.18; 'library': 0.18; 'module': 0.19; 'trying': 0.19; '(but': 0.19; 'command': 0.22; 'import': 0.22; 'aug': 0.22; 'to:name:python-list@python.org': 0.22; 'error': 0.23; 'skip:e 30': 0.24; "haven't": 0.24; 'looks': 0.24; 'skip:" 30': 0.26; 'skip:" 20': 0.27; 'header:In-Reply-To:1': 0.27; '(c)': 0.29; 'character': 0.29; "doesn't": 0.30; 'message-id:@mail.gmail.com': 0.30; 'code': 0.31; 'getting': 0.31; 'subject:what': 0.31; 'file': 0.32; 'text': 0.33; 'up.': 0.33; '(most': 0.33; 'skip:_ 10': 0.34; 'could': 0.34; 'problem': 0.35; 'subject:with': 0.35; 'case,': 0.35; 'received:google.com': 0.35; 'google': 0.35; 'idle': 0.36; "didn't": 0.36; 'subject:?': 0.36; 'so,': 0.37; 'to:addr:python- list': 0.38; 'pm,': 0.38; 'recent': 0.39; 'quote': 0.39; 'to:addr:python.org': 0.39; 'even': 0.60; 'hope': 0.61; 'august': 0.61; 'simply': 0.61; "you've": 0.63; 'name': 0.63; 'due': 0.66; 'here': 0.66; '26,': 0.68; ':).': 0.84; 'messed': 0.84; 'received :mail-ob0-x22d.google.com': 0.84
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=lO+3ajNHSne1/8a9IeIh8tSobjk3Ol9xMfqMI+bKFiM=; b=YNaj0piTEJ3o1C2MxKAt5EBtc8xMA/zd9kC63LdOoiGBiXLp7byCXXie2facsgkfDH /6f5OFbKvhlOuT/06cld8YxrU557d/DEcjyDJ/duj0nV4wWJ78tXn1+j4KevikGGJrkg jwdfHiuM5VOuSmZwIONtWO9WjHXRJBDSd0arzIB8RDb0YWwNdtFFPhH41yaJvBScxDEr xo4kx9ANfSQYrGx//zHYWWEv5GEcqiOpn0Pg6ft4RE5NEtnlNfOYPsyYNouNB/cgJFoO y9Ayai29TBYrW7A84JyWj6g8+bU4EoIk6rlzM+5moNjcbDl/D43axjAXWaoltQEz9ngC eF0w==
X-Received by 10.182.29.101 with SMTP id j5mr29945688obh.20.1409082432205; Tue, 26 Aug 2014 12:47:12 -0700 (PDT)
MIME-Version 1.0
Sender zachary.ware@gmail.com
In-Reply-To <4737dfe9-8a02-46d5-b69b-945199f48a5c@googlegroups.com>
References <4eec9365-4103-4474-a47f-ea665b265b1e@googlegroups.com> <mailman.13475.1409078833.18130.python-list@python.org> <4737dfe9-8a02-46d5-b69b-945199f48a5c@googlegroups.com>
From Zachary Ware <zachary.ware+pylist@gmail.com>
Date Tue, 26 Aug 2014 14:46:52 -0500
X-Google-Sender-Auth MGqCXZ_RW8VMp81P87UbFzZF_Aw
Subject Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?
To "python-list@python.org" <python-list@python.org>
Content-Type text/plain; charset=UTF-8
X-BeenThere python-list@python.org
X-Mailman-Version 2.1.15
Precedence list
List-Id General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive <http://mail.python.org/pipermail/python-list/>
List-Post <mailto:python-list@python.org>
List-Help <mailto:python-list-request@python.org?subject=help>
List-Subscribe <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups comp.lang.python
Message-ID <mailman.13477.1409082441.18130.python-list@python.org> (permalink)
Lines 39
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1409082441 news.xs4all.nl 2951 [2001:888:2000:d::a6]:40776
X-Complaints-To abuse@xs4all.nl
Xref csiph.com comp.lang.python:77071

Show key headers only | View raw


On Tue, Aug 26, 2014 at 2:26 PM, Twirlip2 <ahrodg@googlemail.com> wrote:
> On Tuesday, 26 August 2014 19:46:55 UTC+1, Terry Reedy  wrote:
>> On 8/26/2014 2:01 PM, Twirlip2 wrote:
>>
>> > [...]
>
> Here are the aforementioned error messages (sorry, I didn't realise I could simply "select all" and "copy" text from a command window) - I hope the formatting doesn't get messed up. (I haven't used Google Groups in years.)
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> Traceback (most recent call last):
>   File "I:\Python34\lib\runpy.py", line 170, in _run_module_as_main
>     "__main__", mod_spec)
>   File "I:\Python34\lib\runpy.py", line 85, in _run_code
>     exec(code, run_globals)
>   File "I:\Python34\lib\idlelib\__main__.py", line 8, in <module>
>     import idlelib.PyShell
>   File "I:\Python34\lib\idlelib\PyShell.py", line 18, in <module>
>     from code import InteractiveInterpreter
>   File "E:\Work\Comp\Python\Lib\code.py", line 28
>     path = getenv('PYTHONPATH') + r'\'
>                                      ^
> SyntaxError: EOL while scanning string literal

It looks like the problem is that you've named your module 'code.py',
which is the name of a standard library module used by IDLE.  So, when
IDLE tries to 'from code import InteractiveInterpreter', instead of
getting I:\Python34\lib\code.py, it's getting
E:\Work\Comp\Python\Lib\code.py, which isn't going to work :).

Incidentally, your SyntaxError is due to trying to use r'\' to get a
backslash literal.  Even with r'' strings, backslash will escape a
quote character (but the backslash remains in the string).  In this
case, it's simplest to just use '\\'.

Hope this helps,
-- 
Zach

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


Thread

IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 11:01 -0700
  Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Terry Reedy <tjreedy@udel.edu> - 2014-08-26 14:46 -0400
    Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 12:20 -0700
      Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 12:44 -0700
        Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 12:58 -0700
          Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-08-26 21:15 +0100
        Re: IDLE has suddenly become FAWLTY - so should I be hitting it with   a big stick, or what? Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-08-27 10:03 +1200
          Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 15:55 -0700
            Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-27 08:25 -0700
          Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-27 10:01 +1000
            Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 17:06 -0700
            Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Chris Angelico <rosuav@gmail.com> - 2014-08-27 10:18 +1000
        Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-08-27 00:20 +0100
          Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 16:29 -0700
            Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Terry Reedy <tjreedy@udel.edu> - 2014-08-26 20:51 -0400
              Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 18:11 -0700
                Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Terry Reedy <tjreedy@udel.edu> - 2014-08-27 00:03 -0400
                Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-27 02:12 -0700
    Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 12:26 -0700
      Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Zachary Ware <zachary.ware+pylist@gmail.com> - 2014-08-26 14:46 -0500
  Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Grant Edwards <invalid@invalid.invalid> - 2014-08-26 18:59 +0000
  Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Chris Angelico <rosuav@gmail.com> - 2014-08-27 09:07 +1000
    Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 16:25 -0700
      Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what? Chris Angelico <rosuav@gmail.com> - 2014-08-27 09:42 +1000
      Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-08-27 10:04 +1000
        Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 17:08 -0700
          Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Chris Angelico <rosuav@gmail.com> - 2014-08-27 10:21 +1000
            Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 17:58 -0700
              Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Twirlip2 <ahrodg@googlemail.com> - 2014-08-26 18:06 -0700
              Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Chris Angelico <rosuav@gmail.com> - 2014-08-27 12:36 +1000
                Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Rustom Mody <rustompmody@gmail.com> - 2014-08-26 20:13 -0700
                Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Chris Angelico <rosuav@gmail.com> - 2014-08-27 14:55 +1000
                Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Twirlip2 <ahrodg@googlemail.com> - 2014-08-27 01:50 -0700
              Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-08-27 10:12 +0200
                Re: Python conquors the BBC [was Re: IDLE has suddenly become FAWLTY - so should I be hitting it with a big stick, or what?] Twirlip2 <ahrodg@googlemail.com> - 2014-08-27 02:04 -0700

csiph-web