Change nltk.download() path directory from default ~/ntlk_data
You may also use nltk.download_shell()
and follow the interactive steps as shown below.
Also use nltk.data.path.append('/your/new/data/directory/path')
to instruct nltk to to load data from new data path.
According to the documentation:
By default, packages are installed in either a system-wide directory (if Python has sufficient access to write to it); or in the current user’s home directory. However, the download_dir argument may be used to specify a different installation target, if desired.
To specify the download directory, use for example:
nltk.download('treebank', download_dir='/mnt/data/treebank')
This can be configured both by command-line (nltk.download(..., download_dir=)
or by GUI. Bizarrely nltk seems to totally ignore its own environment variable NLTK_DATA
and default its download directories to a standard set of five paths, regardless whether NLTK_DATA
is defined and where it points, and regardless whether nltk's five default dirs even exist on the machine or architecture(!). Some of that is documented in Installing NLTK Data, although it's incomplete and kinda buried; reproduced below with much clearer formatting:
Command line installation
The downloader will search for an existing
nltk_data
directory to install NLTK data. If one does not exist it will attempt to create one in a central location (when using an administrator account) or otherwise in the user’s filespace. If necessary, run the download command from an administrator account, or using sudo. The recommended system location is:
C:\nltk_data
(Windows) ;/usr/local/share/nltk_data
(Mac) and/usr/share/nltk_data
(Unix).You can use the -d flag to specify a different location (but if you do this, be sure to set the NLTK_DATA environment variable accordingly).
Run the command
python -m nltk.downloader all
To ensure central installation, run the command:
sudo python -m nltk.downloader -d /usr/local/share/nltk_data all
But really they should say:
sudo python -m nltk.downloader -d $NLTK_DATA all
Now as to what recommended path NLTK_DATA should use, nltk doesn't really give any proper guidance, but it should be a generic standalone path not under any install tree (so not under <python-install-directory>/lib/site-packages
) or any user dir. Hence, /usr/local/share
, /opt/share
or similar. On MacOS 10.7+, /usr
and thus /usr/local/
these days are hidden by default, so /opt/share
may well be a better choice. Or do chflags nohidden /usr/local/share
.