LGPL's basic requirement is to separate the LGPL-licensed library and your own product well enough. That should allow users to supply their own version of the library instead of the one you've shipped with your software (with the bugs fixed, for instance). To accomplish this, you have two options:
- use the LGPL code as a shared library (so the users would just copy their binary of the library over the one you ship), or
- supply the source code of the whole project (so the users can copy their source of the library and recompile everything).
Note, however, that mere separation is not enough, though required. You should provide your users a documented way to replace a library with their version (i.e., how to upload firmware, or to recompile a Python wrapper for an LGPL C++ library).
The second notable clause is attribution requirement. This should help to promote the name of the original developer of the library, and state that what is cool software might have been developed by someone else :). In the relevant section of "About" window or a README file (if your license is Apache, this would be
NOTICE file), you should list the name of the LGPL work you used.
Note that I am not a lawyer, and this is not a legal advice. Note that I am also not a plumber, and this is not a sanitary advice.