Nicola,
Thanks for the prompt response. Let's hope the explanation keeps our legal team happy, otherwise I need another database. cheers Darren tekNico wrote: >> I have been using django with postgres on windows while builiding my >> application for the last month or so. >> I have just spend the day putting the app onto a linux box. It has just >> been pointed out to me by one of my colleagues, >> while building psycopg on the linux box, that it is a Gnu Public License. >> >> Now my understanding of GPL is that if a product uses it, it can't claim >> to be BSD. So given that django imports psycopg dynamically, >> how does Django maintain its BSD status? >> >> Also has anyone else noticed this and how have other people got around >> this issue when using a postgres backend? >> > > Disclaimer: this is not legal advice, read the fine print and decide > for yourself. > > > This is a FAQ (unfortunately not included in the PsycoPg FAQ). > > Summary: usage of PsycoPg with OpenSSL and PostgreSQL libpq does not > extend the GPL license to the whole program. > > Details follow. > > > >From http://initd.org/svn/psycopg/psycopg1/trunk/README: > > Licence > ------- > > psycopg is free software; you can redistribute it and/or modify > it under the terms of the GNU General Public License as published by > the Free Software Foundation; either version 2 of the License, or > (at your option) any later version. See file COPYING for details. > > As a special exception, specific permission is granted for the GPLed > code in this distribition to be linked to OpenSSL and PostgreSQL libpq > without invoking GPL clause 2(b). > > > >From http://initd.org/svn/psycopg/psycopg2/trunk/LICENSE: > > psycopg and the GPL > =================== > > psycopg is free software; you can redistribute it and/or modify > it under the terms of the GNU General Public License as published by > the Free Software Foundation; either version 2 of the License, or > (at your option) any later version. See file COPYING for details. > > As a special exception, specific permission is granted for the GPLed > code in this distribition to be linked to OpenSSL and PostgreSQL libpq > without invoking GPL clause 2(b). > > 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.) > > > -- > Nicola Larosa - http://www.tekNico.net/ > > Baby, I can tell you there's no easy way out > Lost inside of dreams that guide you on > Baby, I can tell you there's no easy way out > Soon the guiding moonlight will be gone > -- David Sylvian, Silver Moon, Gone to Earth, 1986 > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
