[EMAIL PROTECTED] wrote: >> Beware that there are some "restrictive" licenses where simply excluding a >> ".py" file does not appear to satisfy the restrictiion. An example of >> this is Qt and PyQt where the restriction on distribution is imposed on >> the Qt library. In such cases, if you exclude a .py wrapper but >> distribute a DLL that a knowledgeable user could employ to gain access to >> the underlying (C/C++) API, then you may still violate the restriction. >> >> I confess that this sort of thing is pretty confusing and some of the >> details and considerations (and the precise conditions under which the >> intended restriction might be violated) are unclear. But there have been >> some pretty complex descriptions of how to satisfy such restrictions (such >> as renaming classes and methods in rebuilding the underlying library so >> that a "knowledgeable user" would not know what symbols to use in >> accessing the library).
IANAL but AFAICR one point is if the program *requires* the module or can use it *if* installed. -- Giovanni Bajo _______________________________________________ PyInstaller mailing list [email protected] http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller
