[PySide] Using PySide for closed source proprietary softwares

[Velummaylum Kajenthiran]

Dear Sir/Madam,I'm using PySide to develop proprietary software application. I haven't done any modification in PySide library. I want to sell my application as closed source to my clients. For this, I plan to use PyInstaller  as a freezing tool.Here I can use --onefile option to ship as one executable. 
Is it violating the licensing terms of PySide? What procedures that I have to follow in order to adhere the legal terms of PySide? 
I have following concerns as well. According to LGPL terms, what's the meaning of dynamic linking in python? as my understanding, it's just an interpreter and everything is linked dynamically. If I use PyInstaller to freeze my application, Is it dynamic linking or static linking? Please clear me the one file option as well. Because if I don't use onefile option, users still can replace the shared Qt libraries by themselves in order to run my application with different versions of Qt/PySide. If I freeze my application as one file exe, users can not replace the so/dll files in order to run my application with different versions of PySide libraries.
I have asked this question in stackoverflow and python mailing list as well. Everyone advised me to contact pyside mailing list for real explanation. Can I get a clear idea about using PySide for my python GUI application? According to license, I should dynamically link to the library to obey the legal terms (Same as Qt). In this case, how do I link dynamically? 

Thank You.Best Regards,Kajenthiran V
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150618/7854e5f2/attachment.html>