Thanks, Steven. I did this, after installing Python 2.4, instead of
2.5. So now I have just Python 2.4 on my Mac OS 10.4.11. Now I find I
can't seem to even import nltk, which I managed to do a couple of days
ago. I get the following:
IDLE 1.1.4
>>> import nltk
Warning (from warnings module):
File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
python2.4/site-packages/nltk/sem/__init__.py", line 24
warnings.warn("nltk.sem.relextract and nltk.sem.chat80 modules not
"
UserWarning: nltk.sem.relextract and nltk.sem.chat80 modules not
loaded (please install sqlite3 library
Traceback (most recent call last):
File "<pyshell#0>", line 1, in -toplevel-
import nltk
File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
python2.4/site-packages/nltk/__init__.py", line 92, in -toplevel-
from yamltags import *
File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
python2.4/site-packages/nltk/yamltags.py", line 1, in -toplevel-
import yaml
ImportError: No module named yaml
>>>
So, parts are still missing? I'm thinking I need to be a whole lot
smarter about about working in Terminal and building and installing
than I am. I also spotted this on the internet in another forum called
Logomacy, in reference to nltk, dated November 6 2007:
"I’ve successfully installed it and got it to run some of the examples
(including the graphing demo) on my Windows box and my Mac OS X
laptop. As is unfortunately typical, although it seems to run better
on the Mac, installing it on Windows was actually a quite a bit
easier. Yeah, yeah, pre-compiled binaries are the work of the devil,
but for Joe end-user–even for a relatively sophisticated Joe end-user–
it’s a pain to get partway through, realize that it won’t compile
because it’s missing some compilers, have to go get the developer
toolkit and install that, and then get back to building the thing you
were trying to get to work in the first place. I didn’t have any
particular problems, other than the time it took to download 183 mb of
stuff that I’ll probably barely use, but it was pretty painful
compared to double-clicking on an exe and then clicking a couple of
buttons. I’m sure hard-core Mac users are so used to the pain that
they don’t even perceive it as pain, and I’m certainly not saying that
the developers of the NLTK ought to devote any time at all to
improving the installation, but if you’re thinking of playing with
this and you aren’t a hard-core Mac user, I’d suggest that if you have
access to both kinds of system, at least to get your feet wet you
should try it in Windows first. You’ll be messing around with the
actual NLTK code a lot faster."
This wasn't exactly encouraging. I think I just have to live with my
failure with my efforts on my Mac and I feel I would be wasting your
time asking for even more help with this . I have Parallels installed
on my Mac and it just seems so much more straightforward to install
and use nltk in Windows XP on my Mac.
John
On May 11, 11:11 pm, Steven Bird <
stevenbi...@gmail.com> wrote:
> 2009/5/12 CorpusLin <
johnnewma...@gmail.com>: