[TriLUG] Software library Kevin Baconess
Keith Woodie via TriLUG
trilug at trilug.org
Wed Jan 13 07:48:59 EST 2021
In general when I am working in python I make sure and use a
requirements.txt file. Most modern IDEs will recognize this and install
the packages as I have requested in the requirements.txt. You can also
use pip to read the requirements.txt file on the command line and install
them for you also. I am fairly sure that is what the IDEs are doing under
the covers. As far as trying to track what the modules I am using are
using inside them ... I try not to worry about that. It really is an
exponential path that really doesn't matter if you organize what you are
using in your own project. Here is a quick link on requirements.txt.
Maybe this will help.
https://www.idkrtm.com/what-is-the-python-requirements-txt/#:~:text=txt%20This%20requirements
.,root%20directory%20of%20your%20project.
Keith Woodie
On Tue, Jan 12, 2021 at 11:53 AM Mauricio Tavares via TriLUG <
trilug at trilug.org> wrote:
> Since some of you work developing code, be it as devops or full
> developers or something else, I was wondering how you keep track of
> which libraries you are building against. For instance, you may be
> doing things in python, which may include a module, which in turn
> relies on other python modules, which then use some C libraries, and
> eventually you get to Kevin Bacon.
>
> That sounds messy.
>
> Is there a clever way to keep track of that? Is there a clever *open
> source* way to do so?
> --
> This message was sent to: Keith Woodie <kwoodie at gmail.com>
> To unsubscribe, send a blank message to trilug-leave at trilug.org from that
> address.
> TriLUG mailing list : https://www.trilug.org/mailman/listinfo/trilug
> Unsubscribe or edit options on the web :
> https://www.trilug.org/mailman/options/trilug/kwoodie%40gmail.com
> Welcome to TriLUG: https://trilug.org/welcome
More information about the TriLUG
mailing list