public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pipenv/
Date: Fri, 27 Oct 2023 03:27:23 +0000 (UTC)	[thread overview]
Message-ID: <1698377196.1efbd7359b98165f31495543c63fe79a57d89b22.sam@gentoo> (raw)

commit:     1efbd7359b98165f31495543c63fe79a57d89b22
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 27 03:26:36 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Oct 27 03:26:36 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1efbd735

dev-python/pipenv: fix WhitespaceFound

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-python/pipenv/pipenv-2023.9.8.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/pipenv/pipenv-2023.9.8.ebuild b/dev-python/pipenv/pipenv-2023.9.8.ebuild
index 6b7786ff6f88..c51698623502 100644
--- a/dev-python/pipenv/pipenv-2023.9.8.ebuild
+++ b/dev-python/pipenv/pipenv-2023.9.8.ebuild
@@ -114,7 +114,7 @@ src_prepare() {
 	done
 
 	sed --in-place -e "s/pipenv.vendor.pythonfinder.utils.get_python_version/pythonfinder.utils.get_python_version/g" tests/unit/test_utils.py || die "Failed patching tests"
-	
+
 	rm -Rfv pipenv/vendor || die "Could not vendor"
 	rm -Rfv examples || die "Could not remove examples"
 }


             reply	other threads:[~2023-10-27  3:27 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27  3:27 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-12  7:28 [gentoo-commits] repo/gentoo:master commit in: dev-python/pipenv/ Michał Górny
2024-10-12  7:04 Michał Górny
2024-09-27  5:57 Eli Schwartz
2024-09-27  5:57 Eli Schwartz
2024-08-17  7:39 Michał Górny
2024-08-15  5:44 Joonas Niilola
2024-07-13  7:35 Joonas Niilola
2024-04-22 10:58 Michał Górny
2024-03-13  0:54 Sam James
2024-03-12 15:43 Michał Górny
2024-03-12 15:43 Michał Górny
2024-01-06 14:08 Michał Górny
2023-12-30 18:30 Michał Górny
2023-12-15 15:33 Jakov Smolić
2023-12-13 10:10 Andrew Ammerlaan
2023-12-03  8:39 Andrew Ammerlaan
2023-12-03  8:39 Andrew Ammerlaan
2023-12-02 19:31 Jakov Smolić
2023-09-16  7:57 Joonas Niilola
2023-09-16  7:57 Joonas Niilola
2023-09-16  7:57 Joonas Niilola
2023-09-16  7:57 Joonas Niilola
2023-05-21  5:43 Sam James
2023-01-20 14:01 Joonas Niilola
2022-12-24  7:03 Sam James
2022-11-14  4:44 Michał Górny
2022-10-09 16:34 Joonas Niilola
2022-10-09 16:34 Joonas Niilola
2022-10-09 16:34 Joonas Niilola
2022-10-02 18:54 Arthur Zamarin
2022-10-02 18:54 Arthur Zamarin
2022-09-09  7:23 Arthur Zamarin
2022-09-09  7:23 Arthur Zamarin
2022-07-05  8:52 Joonas Niilola
2022-06-16  8:08 Michał Górny
2022-06-07 18:56 Arthur Zamarin
2022-05-25 17:11 Patrick McLean
2022-05-24 21:52 Patrick McLean
2022-04-19  5:56 Arthur Zamarin
2022-03-30 11:25 Jakov Smolić
2022-01-19 13:44 Jakov Smolić
2022-01-18 12:36 Sam James
2022-01-09  1:23 Sam James
2021-10-17  9:13 Michał Górny
2021-08-18 13:33 Joonas Niilola
2021-06-01  0:28 Sam James
2021-06-01  0:28 Sam James
2021-02-27 21:07 Sam James
2020-12-13 10:44 Joonas Niilola
2020-12-13 10:44 Joonas Niilola
2020-11-11 21:26 Patrice Clement
2020-10-12 12:39 Joonas Niilola
2020-07-27 13:14 Michał Górny
2020-07-27 13:11 Michał Górny
2020-07-27 13:11 Michał Górny
2020-07-27 13:11 Michał Górny
2020-04-16  8:38 Michał Górny
2020-04-16  8:38 Michał Górny
2020-03-28 11:59 Michał Górny
2019-12-16 13:48 Sebastian Pipping
2018-11-10 14:25 Justin Lecher
2018-08-06 19:41 Patrick Lauer
2018-02-01  8:47 Michał Górny
2018-02-01  8:47 Michał Górny
2017-12-09 15:04 Justin Lecher
2017-12-02 20:51 Justin Lecher
2017-12-02 20:09 Justin Lecher
2017-12-02 17:27 Justin Lecher

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=1698377196.1efbd7359b98165f31495543c63fe79a57d89b22.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox