Title: Unable to run NLTK on Jython 2.5 final
Type: behaviour Severity: normal
Components: Any Versions: 2.5.0
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: amak, brice.fernandes, pjenvey, raghavanks
Priority: normal Keywords:

Created on 2009-07-12.09:28:07 by raghavanks, last changed 2011-11-07.22:26:57 by amak.

msg4899 (view) Author: Raghavan (raghavanks) Date: 2009-07-12.09:28:06
I tried to run NLTK 0.99 on Jython 2.5 (final) expecting it to work
since nltk was compatible with cPython 2.5. I got the following errors
though (pointing to some missing zlib constants in Jython 2.5) .

>>> import nltk                                         
nltk.sem.relextract and nltk.sem.chat80 modules not loaded (please
install sqlite3
  warnings.warn("nltk.sem.relextract and nltk.sem.chat80 modules not "
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/raghavan/mystuff/nltk0.99/nltk-0.9.9/nltk/",
line 96, in
    import data
  File "/home/raghavan/mystuff/nltk0.99/nltk-0.9.9/nltk/", line
44, in <module>
    from zlib import Z_SYNC_FLUSH
ImportError: cannot import name Z_SYNC_FLUSH

Comments (from Frank Wierzbicki's Weblog -

It looks like we are missing a few constants in zlib, I bet they are
either new since 2.2/2.3 and haven't been added or they are somehow
incompatible with Java's compression support (I'm not up on this stuff
at the moment)
msg4901 (view) Author: Philip Jenvey (pjenvey) Date: 2009-07-15.06:03:06
Java's zip implementation doesn't support any partial flush modes like 
bug_id=4255743), so we've disabled these modes and their associated 
flags. That way libs fail fast when trying to use it

However we should probably provide the flags for compatibility sake 
anyway. ntlk doesn't even seem to rely on this flush mode, it just 
references it because it subclasses gzip.GzipFile.flush which references 
it (as it's the default mode).

Our own GzipFile has a workaround for the lack of zlib.Z_SYNC_FLUSH, so 
supporting it would also rid us of that
msg4902 (view) Author: Philip Jenvey (pjenvey) Date: 2009-07-15.06:12:00
Actually our flush() is going to eventually reject the unsupported mode 
anyway, which means if we added the flag it's just going to delay the 
error till later
msg5765 (view) Author: Alan Kennedy (amak) Date: 2010-05-11.08:32:05
I haven't been following this bug, but NLTK appear to have adopted a workaround for this problem.
msg6718 (view) Author: Alan Kennedy (amak) Date: 2011-11-07.22:26:57
NLTK fixed this issue 18 months ago.
Date User Action Args
2011-11-07 22:26:57amaksetstatus: open -> closed
resolution: wont fix
messages: + msg6718
2010-05-11 08:32:06amaksetnosy: + amak
messages: + msg5765
2009-07-28 10:58:33brice.fernandessetnosy: + brice.fernandes
2009-07-15 06:12:00pjenveysetmessages: + msg4902
2009-07-15 06:03:07pjenveysetpriority: normal
nosy: + pjenvey
messages: + msg4901
2009-07-12 09:28:20raghavankssettype: behaviour
2009-07-12 09:28:07raghavankscreate