I had also been wondering about this paragraph. However given the presence of a paragraph asking money I think that one will have precedence to the other one (would make sense no ?).
However, do you consider psycopg part of dabodev distribution (in which case the licensing becomes your liability (ie you cannot release under your current license as gpl overrides any other license ?)) or do you consider this as responsibility of the end user ? Our lawyers are adamant that GPL is a nono for what we intend to do. So if I create a dabo app it must be free of GPL code as I am not allowed to distribute our source code. Can dabo use some odbc interface with a better licensing scheme ? Changing db is no option either. fuzzy lawyer speak: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Note that the GPL was chosen to avoid proprietary adapters based on psycopg code. Using psycopg in a proprietary product (even bundling psycopg with the proprietary product) is fine as long as: 1. psycopg is called from Python only using only the provided API (i.e., no linking with C code and no C modules based on it); and 2. all the other points of the GPL are respected (you offer a copy of psycopg's source code, and so on.) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
