Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Let's answer these in reverse order:</p> <blockquote> <p>How can I sort the mess of having too many Python versions? </p> </blockquote> <p>Get rid of the extras!</p> <p>Having Python 2.x and 3.x in parallel is fine. Having Python 2.x and 2.y or 3.x and 3.y in parallel is fine, as long as you remember to always use the specific versions of everything (e.g., run <code>python2.7</code> instead of <code>python</code>, or <code>pip-3.3</code> instead of <code>pip3</code>). Having Python 2.x.y and 2.x.z in parallel (or two different 2.x.y) is a big problem. Unless you really need to do it for some reason, don't put yourself through the headache. Just stick with Apple's 2.7.5 (Mavericks) or 2.7.2 (Snow Leopard through Mountain Lion). See <a href="http://stupidpythonideas.blogspot.com/2013/02/sticking-with-apples-python-27.html" rel="nofollow">this blog post</a> for more details.</p> <p>So, how do you get rid of your extra Python 2.7.5? That depends entirely on how you installed it. If you used a package manager like <code>brew</code> or <code>port</code>, it will have an uninstall command; if you used an installer package, it may or may not have come with an uninstaller; in some cases, you may have to manually track down and delete everything. Since you haven't said how you installed 2.7.5, I can't give any specific instructions. But if you search this site or Google with the appropriate information, like "uninstall ActiveState Python Mac", you'll find them pretty quickly on your own.</p> <blockquote> <p>How can I install NLTK … through the Terminal using Python 2.7.5?</p> </blockquote> <p>Most likely the top <code>pip</code> on your PATH is the one that goes with Apple's Python 2.7, but the top <code>python</code> on your PATH is the one that goes with your other 2.7. And this is exactly the kind of problem you get by having two Python 2.7 versions. If you want to learn about how to figure out what's where and how PATH finds things, how Python/easy_install/pip decides where to put things that it installs, where your multiple site-packages are, how pig-resources works, etc., then go learn all of that and you will be able to make this work. Otherwise, don't try it.</p> <blockquote> <p>How can I install NLTK on … Python 3.3.</p> </blockquote> <p>You can't. As <a href="http://nltk.org/install.html" rel="nofollow">the homepage</a> says, "NLTK requires Python versions 2.6-2.7." 3.3 is not 2.6-2.7.</p> <p>There is a port to Python 3, but it's (a) a separate project, (b) still in alpha, and (c) not yet installable via <code>pip</code>.</p> <hr> <p>In summary:</p> <p>Keep your Python 3.3; it's not hurting anything. But don't try to use NLTK with it.</p> <p>Get rid of your extra Python 2.7; it's the cause of all of your problems.</p> <p>Once you've cleaned up the extra Python 2.7, install NLTK by following the instructions.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload