Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9247885
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T09:50:53+00:00 2026-06-18T09:50:53+00:00

Running OS X 10.6.8 Snow Leopard I cannot input the scandinavian letters into the

  • 0

Running OS X 10.6.8 Snow Leopard I cannot input the scandinavian letters into the interpretive mode. The terminal bell sounds for every keystroke and nothing shows up. All letters show up as normal in the regular terminal environment. Inputting UTF8 characters works fine in the Terminal, when running a python script, in PyDev and in the REPL

Is there a problem with the interactive mode settings and these special characters?

I have installed and am running python 2.7.3 mainly, but the OS-provided Pythons have this problem too. (i.e when running python2.5 or python2.6 I still experience this problem.) I dont know if installing python 2.7 has changed some under library that it uses, maybe readline (I’m on thin ice here, guessing basically)?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-18T09:50:55+00:00Added an answer on June 18, 2026 at 9:50 am

    It sounds like the problem here is that the python.org Python is expecting real readline, and not being happy with the libedit substitute that Apple provides.

    See the documentation for readline at PyPI for an explanation of the issue.

    You can fix it as follows:

    sudo /path/to/easy_install readline
    

    Note that readline is one of the handful of things that cannot be installed properly by pip, so you have to use easy_install (or do it manually).

    The python.org 2.x installers don’t come with easy_install. Install it by following the directions on the setuptools page.

    On top of that, keep in mind that, in some cases, you can end up with Apple-python easy_install in /usr/local/bin as well as /usr/bin, which means you can’t be sure /usr/local/bin/easy_install will get the python.org version, so explicitly use easy_install-X.Y.

    And even that doesn’t help if you’re using a python.org (or other) installation of an X.Y version that Apple already gave you. /usr/local/bin/easy_install-2.7 may well be Apple’s (as it is on the 10.8.2 machine I’m sitting at right now). The only way to be safe is to check the shebang line and see which Python interpreter it uses.

    Or, more simply, just don’t install a python-X.Y if Apple’s already given you one. Seriously, there are hundreds of questions all over SO from people who did this and have problems, and all of them could be avoided by just using the Apple build. Apple used to ship broken, incomplete, and/or woefully out-of-date Python, but since either 10.5 or 10.6, they’ve been shipping working, complete, reasonably-recent versions, with extras like easy_install and PyObjC included.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Im running Mac OS X Snow Leopard 10.6. When trying to get into phpMyAdmin,
I am using a Mac OS running Snow Leopard 10.6.8 and RVM 1.10.3, Ruby
I'm running Mac OSX Snow Leopard, this problem is caused by a recent train
I'm running Mac OS X 10.6.x (Snow Leopard) right now, so I'm pretty sure
I just upgraded to snow leopard. Before, I had everything running fine, but now
I have a MacBook Pro running Snow Leopard; how can I see what version
I'm currently running Snow Leopard and I have Xcode 3.2.6 installed. I'd like to
My company is still running Snow Leopard and we're thinking about upgrading to Mountain
I'm developing a web application in PHP, and my Macbook, running Snow Leopard, is
I am using a Mac OS running Snow Leopard 10.6.8, Ruby on Rails 3.2.2

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.