NLTK 3 on 64 bit Python/Win7

[Gary Daine]

Hi,
I'm trying to install NLTK 3 on a 64-bit Python under Win7.
The .exe installer fails because it can't find Python in the Registry (it's
obviously checking the 32-bit side only).
I downloaded the .zip file and installed that, and it seemed to work, but
'import nltk' throws a 'Floating point overflow' message (under PyScripter).
It looks as though only some parts of NLTK are loaded - 'nltk.download()'
doesn't work, for example.

I want to stick with the 64-bit version of Python if possible, to make use of
all the available memory rather than the 4GB that 32bits gives me.
Is this possible at present, or should I just resign myself to recoding for 32 bits?

Thanks,
Gary

[Harsh Thakkar]

Dear Gary,

You have raised a valid point, before 2 months i tried the same, but no success. I found some tweaks for the same but still nothing seemed to work. It  seems like working python 64bit + W7 and NLTK 3.0 is the deadliest combination. I resigned to python 32 bit, and now i cant make use of files more than 4 GB.

p.s. i wrote a classifier which is being tuned on .dat files more than 4 GB, it fails. Anythign less than 4 GB works fine. Let me know if anybody finds a solution. I personally feel python community has no proper support for 64 bit windows 7 users :( #sad

Thank you for your time and consideration,
Harsh V. Thakkar

Research Enthusiast |Computer Science |M.Tech 2011 

Sardar Vallabhbhai National Institute of Technology

Surat  |Gujarat |INDIA 395 007

Contact: +91-9824547890 

Facebook |LinkedIn |Twitter |Web 

"People cannot go wrong, if you don't let them.  They cannot go right,

unless you let them."

--
You received this message because you are subscribed to the Google Groups "nltk-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nltk-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Mikhail Korobov]

Hi Gary and Harsh,

What Python version and NLTK version do you use?

What do you mean by 'Floating point overflow' - is it a traceback (the posting a full traceback would be helpful) or is it a warning or something else? Warnings usually have filenames and line numbers in their message, so posting full warning could be helpful.

"nltk.download() doesn't work" - does it mean it throws an exception? Some nltk.download() issues were fixed in github master branch since NLTK 3.0a1, so downloading NLTK from here: https://github.com/nltk/nltk could fix the error (if you don't use git, there is "ZIP" button for downloading source as a zip archive).

NLTK 3.0 alpha was released exactly to gather such bug reports :) So it'll be appreciated if you find time to share more information about your issues; the best place to share it is NLTK bugtracker: https://github.com/nltk/nltk/issues?direction=desc&sort=updated&state=open . Without more information and community help issues such as yours could be hard to fix. 

суббота, 27 апреля 2013 г., 18:03:41 UTC+6 пользователь harsh9t написал:

To unsubscribe from this group and stop receiving emails from it, send an email to nltk-users+...@googlegroups.com.

[Gary Daine]

Sorry for not giving more details, but I was really just asking whether it was worth even trying to install NLTK on a 64 bit system.

As it stands I don't know whether it's a problem with NLTK itself, a corrupted download, or with PyScripter itself.

For the record, I'm using 64-bit Python 3.3.0 on 64-bit Win7 Pro, and NLTK 3.0a0.zip.

The 'floating point overflow' error is a PyScripter error message and references python33.dll plus a whole load of other non-Python related dlls, which is why I say it might be a pyScripter error, and nltk.download() throws an error message: 'name 'nltk' is not defined', suggesting that the installation did not go as it should have.

Since it appears from your message that it should be possible, I'll start again tomorrow with version 3.0a1 and document things properly.

Gary

On 28/04/2013 0:25, Mikhail Korobov wrote:

Hi Gary and Harsh,

What Python version and NLTK version do you use?

What do you mean by 'Floating point overflow' - is it a traceback (the posting a full traceback would be helpful) or is it a warning or something else? Warnings usually have filenames and line numbers in their message, so posting full warning could be helpful.

"nltk.download() doesn't work" - does it mean it throws an exception? Some nltk.download() issues were fixed in github master branch since NLTK 3.0a1, so downloading NLTK from here:О©╫https://github.com/nltk/nltk could fix the error (if you don't use git, there is "ZIP" button for downloading source as a zip archive).

NLTK 3.0 alpha was released exactly to gather such bug reports :) So it'll be appreciated if you find time to share more information about your issues; the best place to share it is NLTK bugtracker:О©╫https://github.com/nltk/nltk/issues?direction=desc&sort=updated&state=open . Without more information and community help issues such as yours could be hard to fix.О©╫

О©╫О©╫О©╫О©╫О©╫О©╫О©╫, 27 О©╫О©╫О©╫О©╫О©╫О©╫ 2013О©╫О©╫., 18:03:41 UTC+6 О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫ harsh9t О©╫О©╫О©╫О©╫О©╫О©╫О©╫:

Dear Gary,

You have raised a valid point, before 2 months i tried the same, but no success. I found some tweaks for the same but still nothing seemed to work. It О©╫seems like working python 64bit + W7 and NLTK 3.0 is the deadliest combination. I resigned to python 32 bit, and now i cant make use of files more than 4 GB.

p.s. i wrote a classifier which is being tuned on .dat files more than 4 GB, it fails. Anythign less than 4 GB works fine. Let me know if anybody finds a solution. I personally feel python community has no proper support for 64 bit windows 7 users :( #sad

Thank you for your time and consideration,
Harsh V. Thakkar

Research Enthusiast |Computer ScienceО©╫|M.Tech 2011О©╫

Sardar Vallabhbhai National Institute of Technology

SuratО©╫ |Gujarat |INDIA 395 007

Contact: +91-9824547890О©╫

FacebookО©╫|LinkedInО©╫|TwitterО©╫|WebО©╫

"People cannot go wrong, if you don't let them. О©╫They cannot go right,

unless you let them."

On Sat, Apr 27, 2013 at 4:40 PM, Gary Daine <gda...@gmail.com> wrote:

Hi,
I'm trying to install NLTK 3 on a 64-bit Python under Win7.
The .exe installer fails because it can't find Python in the Registry (it's obviously checking the 32-bit side only).
I downloaded the .zip file and installed that, and it seemed to work, but 'import nltk' throws a 'Floating point overflow' message (under PyScripter).
It looks as though only some parts of NLTK are loaded - 'nltk.download()' doesn't work, for example.

I want to stick with the 64-bit version of Python if possible, to make use of all the available memory rather than the 4GB that 32bits gives me.
Is this possible at present, or should I just resign myself to recoding for 32 bits?

Thanks,
Gary

--
You received this message because you are subscribed to the Google Groups "nltk-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nltk-users+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "nltk-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nltk-users+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

О©╫
О©╫

[Gary Daine]

Update:

I was able to install 3.0a1 from Github, and it works fine from Idle and in a DOS window, but not from PyScripter, so I have at least located the source of the original error.
I was able to download the corpora and run some simple tests, so to answer my own question, yes, NLTK does work on 64 bit Python 3.3/64 bit Windows 7.

Thanks for the help.

Gary

[Mikhail Korobov]

Hi Gary,

Thanks for the investigation! 

понедельник, 29 апреля 2013 г., 18:04:47 UTC+6 пользователь gdaine написал: