unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Cully via Guix-patches via <guix-patches@gnu.org>
To: 60436@debbugs.gnu.org
Cc: Brian Cully <bjc@spork.org>
Subject: [bug#60436] [PATCH] gnu: Add python-setuptools-lint.
Date: Fri, 30 Dec 2022 16:42:02 -0500	[thread overview]
Message-ID: <d41be2518bb150cb647bbad8cdcd687df9619dce.1672436522.git.bjc@spork.org> (raw)

* gnu/packages/check.scm: (python-setuptools-lint) New variable.
---
 gnu/packages/check.scm | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/gnu/packages/check.scm b/gnu/packages/check.scm
index aaa41777dc..7c351fb1ac 100644
--- a/gnu/packages/check.scm
+++ b/gnu/packages/check.scm
@@ -2672,6 +2672,23 @@ (define-public python-pylint
 possible to write plugins to add your own checks.")
     (license license:gpl2+)))
 
+(define-public python-setuptools-lint
+  (package
+    (name "python-setuptools-lint")
+    (version "0.6.0")
+    (source (origin
+              (method url-fetch)
+              (uri (pypi-uri "setuptools-lint" version))
+              (sha256
+               (base32
+                "16a1ac5n7k7sx15cnk03gw3fmslab3a7m74dc45rgpldgiff3577"))))
+    (build-system python-build-system)
+    (propagated-inputs (list python-pylint))
+    (home-page "https://github.com/johnnoone/setuptools-pylint")
+    (synopsis "Setuptools command for pylint")
+    (description "Setuptools command for pylint")
+    (license license:bsd-3)))
+
 (define-public python-paramunittest
   (package
     (name "python-paramunittest")
-- 
2.38.1





             reply	other threads:[~2022-12-30 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 21:42 Brian Cully via Guix-patches via [this message]
2023-02-06  7:06 ` bug#60436: [PATCH] gnu: Add python-setuptools-lint 宋文武 via Guix-patches via

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=d41be2518bb150cb647bbad8cdcd687df9619dce.1672436522.git.bjc@spork.org \
    --to=guix-patches@gnu.org \
    --cc=60436@debbugs.gnu.org \
    --cc=bjc@spork.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).