All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nicky Chorley <ndchorley@gmail.com>
Cc: linux-spdx@vger.kernel.org
Subject: Re: Fwd: scripts/spdxcheck.py's third-party dependencies
Date: Tue, 27 Jul 2021 08:47:38 +0200	[thread overview]
Message-ID: <YP+sCqNlB2g/srHc@kroah.com> (raw)
In-Reply-To: <CAG-xSoY-Z=AD8KhXrJvzqgA+mYZwUGEbAQ7UfPEbH6e4g7VD4w@mail.gmail.com>

On Tue, Jul 27, 2021 at 07:42:21AM +0100, Nicky Chorley wrote:
> Resending to linux-spdx.
> 
> ---------- Forwarded message ---------
> From: Nicky Chorley <ndchorley@gmail.com>
> Date: Sun, 25 Jul 2021 at 20:35
> Subject: scripts/spdxcheck.py's third-party dependencies
> To: <tglx@linutronix.de>, <gregkh@linuxfoundation.org>
> 
> 
> Hi folks,
> 
> On linux-next (tag: next-20210723), running scripts/checkpatch.pl
> complains, with e.g.
> 
> Traceback (most recent call last):
>    File "scripts/spdxcheck.py", line 10, in <module>
>      import git
> ModuleNotFoundError: No module named 'git'
> 
> and the same for ply if you don't have those libraries installed. Would it
> be OK to add a pip requirements.txt file, so that people can use that to
> install those and not have to manually go hunt them down? In future,
> if other Python scripts needed third-party libraries, those could be
> listed in the file too (I had a quick look and didn't see any used in the
> others).
> 
> Apologies if this has already been covered somewhere - I couldn't see
> archive links for linux-spdx on vger.kernel.org.

How can you add a requirements.txt file for a single script in a
directory of other scripts?

thanks,

greg k-h

  reply	other threads:[~2021-07-27  6:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <efcdf26-fd74-3d7d-25b1-d77ed3c493@rigel.lan>
2021-07-27  6:42 ` Fwd: scripts/spdxcheck.py's third-party dependencies Nicky Chorley
2021-07-27  6:47   ` Greg KH [this message]
2021-07-31 11:57     ` Nicky Chorley
2021-08-05 12:21       ` Greg KH
2021-08-06  6:44         ` Nicky Chorley
2021-08-10 11:27           ` Zavras, Alexios
2021-08-10 16:57           ` Christoph Hellwig
2021-08-10 21:00             ` Thomas Gleixner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YP+sCqNlB2g/srHc@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=ndchorley@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.