From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/django-cors-headers/
Date: Sun, 17 Apr 2022 19:00:20 +0000 (UTC) [thread overview]
Message-ID: <1650221991.867b2fbde1d060ac3dc8cd88f80cb57abe529510.sam@gentoo> (raw)
commit: 867b2fbde1d060ac3dc8cd88f80cb57abe529510
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 17 18:51:51 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Apr 17 18:59:51 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=867b2fbd
dev-python/django-cors-headers: drop 3.10.1
Signed-off-by: Sam James <sam <AT> gentoo.org>
| 25 ----------------------
1 file changed, 25 deletions(-)
diff --git a/dev-python/django-cors-headers/django-cors-headers-3.10.1.ebuild b/dev-python/django-cors-headers/django-cors-headers-3.10.1.ebuild
deleted file mode 100644
index 441ad19af723..000000000000
--- a/dev-python/django-cors-headers/django-cors-headers-3.10.1.ebuild
+++ /dev/null
@@ -1,25 +0,0 @@
-# Copyright 1999-2021 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-PYTHON_COMPAT=( python3_{8..10} )
-inherit distutils-r1
-
-DESCRIPTION="Django App that adds CORS (Cross-Origin Resource Sharing) headers to responses"
-HOMEPAGE="https://github.com/adamchainz/django-cors-headers"
-SRC_URI="
- https://github.com/adamchainz/django-cors-headers/archive/${PV}.tar.gz
- -> ${P}.gh.tar.gz"
-
-LICENSE="MIT"
-SLOT="0"
-KEYWORDS="~amd64"
-
-RDEPEND=">=dev-python/django-2.2[${PYTHON_USEDEP}]"
-BDEPEND="
- test? (
- dev-python/pytest-django[${PYTHON_USEDEP}]
- )"
-
-distutils_enable_tests pytest
next reply other threads:[~2022-04-17 19:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 19:00 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-19 12:29 [gentoo-commits] repo/gentoo:master commit in: dev-python/django-cors-headers/ Michał Górny
2025-09-19 12:29 Michał Górny
2025-09-09 3:22 Michał Górny
2025-02-07 5:45 Michał Górny
2025-02-07 5:45 Michał Górny
2024-10-30 3:41 Michał Górny
2024-10-30 3:41 Michał Górny
2024-10-13 3:10 Michał Górny
2024-06-20 17:14 Michał Górny
2024-06-20 4:45 Michał Górny
2023-12-30 18:28 Michał Górny
2023-11-14 20:06 Michał Górny
2023-10-11 16:49 Michał Górny
2023-07-28 15:58 Michał Górny
2023-07-24 11:31 Michał Górny
2023-07-11 5:52 Michał Górny
2023-06-14 16:11 Michał Górny
2023-05-13 4:46 Michał Górny
2023-02-26 4:57 Michał Górny
2023-02-26 4:57 Michał Górny
2022-06-16 8:05 Michał Górny
2022-06-06 5:26 Michał Górny
2022-06-04 17:48 Michał Górny
2022-05-16 13:17 Michał Górny
2022-05-11 8:05 Michał Górny
2022-02-26 17:59 Michał Górny
2022-02-26 17:59 Michał Górny
2021-12-05 21:42 Michał Górny
2021-10-17 7:41 Michał Górny
2021-10-06 7:46 Michał Górny
2021-09-29 8:16 Michał Górny
2021-08-16 7:30 Michał Górny
2021-05-15 23:15 William Hubbs
2021-01-30 20:27 Conrad Kostecki
2021-01-30 20:27 Conrad Kostecki
2020-12-11 14:51 Michał Górny
2020-03-26 20:52 Michał Górny
2020-02-11 20:10 William Hubbs
2020-01-26 20:06 William Hubbs
2019-07-11 22:09 William Hubbs
2019-06-29 9:17 Michał Górny
2019-03-27 21:07 William Hubbs
2019-03-14 20:26 William Hubbs
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=1650221991.867b2fbde1d060ac3dc8cd88f80cb57abe529510.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