License LPGL and commercialization

I have recently been told by outside council (lawyers) that our organization is unable to use LGPL licensed packages in software we plan to sell.
We have already built a web app using Python + Django.

Ticket:
#461 (Support use of pypgsql instead of psycopg) - Django (djangoproject.com)<https://code.djangoproject.com/ticket/461>
Seems to suggest the purpose of the LGPL license is not to prevent the intended use we have in mind (selling the web app to be hosted locally at other organizations). Instead it is to prevent other from building off the drivers and then selling those drivers.

Is that the case? Is our intended purpose within the license constraints outlined? Can we receive written confirmation that our intended use won't come back to hurt us and we have permission? Or can we not use your package in this way? We will be compliant with whatever outcome is required. If we need to move away from Django (psycopg2) then we can do that if needed.

Brian Hunt
Data Scientist I, Advanced Analytics
OSF HealthCare System
1306 N. Berkeley Ave. | Peoria, IL | 61603
p 309-308-9657 | f 309-308-0530
www.osfhealthcare.org<http://www.osfhealthcare.org/>
Facebook<http://www.facebook.com/osfhealthcare> | Twitter<http://www.twitter.com/osfhealthcare> | YouTube<http://www.youtube.com/osfhealthcare>
"Serving with the Greatest Care and Love"

====================
The information in this message is confidential and may be legally privileged. Access to this message by anyone other than the addressee is not authorized. If you are not the intended recipient, or an agent of the intended recipient, any disclosure, copying, or distribution of the message or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please contact the sender immediately and permanently delete the original e-mail, attachment(s), and any copies.
====================