all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Graves via Guix-patches via <guix-patches@gnu.org>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 70570@debbugs.gnu.org
Subject: [bug#70570] [PATCH 1/2] guix: import: pypi: Ignore pypi-ignored-inputs.
Date: Fri, 26 Apr 2024 12:23:30 +0200	[thread overview]
Message-ID: <87jzkkv2vx.fsf@ngraves.fr> (raw)
In-Reply-To: <ZitlNNs1jvQiF-BY@noor.fritz.box>

On 2024-04-26 10:26, Lars-Dominik Braun wrote:

> Hi,
>
>> +(define pypi-ignored-inputs
>> +  ;; This list contains packages that are useful for development or quality
>> +  ;; testing, but that most of the time are not necessary to have as an input.
>> +  (list "argparse"  ; native
>> +        "codecov" "coverage"  ; coverage
>> +        "black" "isort" "pycodestyle" "pep8"  ; style
>> +        "pyflakes" "flake8" "pylint" "mypy"  ; style+lint
>> +        "coveralls" "twine"  ; upload integration tools
>> +        "pytest-isort" "pytest-flake8" "pytest-cov" "pytest-black"
>> +        "pytest-pep8" "pytest-mypy" "pytest-pep8" "pre-commit"))  ; variants
>
>> +  (let ((input-names (append
>> +                      '("python-setuptools"
>> +                        "python-pip"
>> +                        "python-pre-commit")
>> +                      pypi-ignored-inputs)))
>
> we should remove python-setuptools from this list now (since it actually
> should be an input on the python-team branch), python-pre-commit is
> also part of pypi-ignored-inputs and maybe we can just add pip to
> pypi-ignored-inputs and use only that list?

Yes, but then it should be done in an independent commit IMO to keep
this one focused on native-inputs and pytest, and then add one for your
other changes of the build system.

But yes, I think they ought to be in the same list.

>
> Also note that check-inputs-should-not-be-an-input-at-all expects Guix
> package names (with python- prefix), whereas pypi-ignored-inputs uses
> Python package names, so you probably want to (map (cut (string-append
> "python-" <>) …) (or similar) here.

Perfectly right, thanks for noticing.

About pre-commit : if we add the python- prefix, then we use the
outdated variable. Maybe we should remove if pypi-ignored-inputs here,
and add "pre-commit" idependently.


> Lars
>

Another quick note : The plugin could also be several plugins (one per
package) in the store added in the PYTHONPATH, which would enable us to
not regenerate the file everytime, but it doesn't compile with (guix
gexp) module. It might be more efficient / guixy this way, but I'm not
able to do it.

If you know how to, don't hesitate ;)

-- 
Best regards,
Nicolas Graves




  reply	other threads:[~2024-04-26 10:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 15:42 [bug#70570] [PATCH 0/2] Python: Ignore unwanted development inputs Nicolas Graves via Guix-patches via
2024-04-25 15:59 ` [bug#70570] [PATCH 1/2] guix: import: pypi: Ignore pypi-ignored-inputs Nicolas Graves via Guix-patches via
2024-04-25 15:59   ` [bug#70570] [PATCH 2/2] guix: pyproject-build-system: Ignore unwanted pytest flags Nicolas Graves via Guix-patches via
2024-04-26  8:47     ` Lars-Dominik Braun
2024-04-26 10:14       ` Nicolas Graves via Guix-patches via
2024-04-27 16:09         ` Nicolas Graves via Guix-patches via
2024-04-26  8:26   ` [bug#70570] [PATCH 1/2] guix: import: pypi: Ignore pypi-ignored-inputs Lars-Dominik Braun
2024-04-26 10:23     ` Nicolas Graves via Guix-patches via [this message]
2024-04-27 16:54 ` [bug#70570] [PATCH v2 " Nicolas Graves via Guix-patches via
2024-04-27 16:54   ` [bug#70570] [PATCH v2 2/2] guix: pyproject-build-system: Ignore unwanted pytest flags Nicolas Graves via Guix-patches via
2024-04-28 10:14     ` Nicolas Graves 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

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

  git send-email \
    --in-reply-to=87jzkkv2vx.fsf@ngraves.fr \
    --to=guix-patches@gnu.org \
    --cc=70570@debbugs.gnu.org \
    --cc=lars@6xq.net \
    --cc=ngraves@ngraves.fr \
    /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 external index

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

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.