On 4/27/2007 12:24 AM, pythonista wrote: >> I've added PyEnchant-1.3.0 to my program and cannot get PyInstaller >> 1.3 to package it. PyEnchant stores its dictionaries in C: >> \Python24\Lib\site-packages\enchant\share\enchant\myspell\. The files >> in here are plain text files: en_US.dic, en_US.aff, etc. ... > > I finally found what I need to do. For the record, from > http://sourceforge.net/mailarchive/forum.php?thread_name=45346C4B.5070801%40rfk.id.au&forum_name=pyenchant-users > "You need to copy both the "share" and "lib" dirs from the enchant > site-packages directory nto the dir of the exe. "share" contains the > dictionaries themselves, while "lib" contains the enchant myspell > plugin."
OK. That can be taken care of using a setup program like InnoSetup. Anyway, I would like this to be fixed automatically by PyInstaller. There is much infrastructure in place to pack trees of data files into the executable, unpack automatically them at startup, and let the package find them. This is the way the Tkinter support works, for instance. Alas, that support is currently hardcoded for Tkinter. It would have to be generalized, so that one can write something like an extended import hook to handle that. It's not that hard to do, but I don't have time right now to do it. But I would appreciate if you could open a ticket on the website reporting the exact problem and the findings you reported on the mailing list. This will make sure I won't forget about this, and I'll eventually have this fixed. Thanks! -- Giovanni Bajo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en -~----------~----~----~----~------~----~------~--~---
