From: UsernameRandomlyGenerated <UsernameRandomlyGenerated@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python-pycodestyle: update to 2.7.0.
Date: Sun, 28 Mar 2021 18:13:58 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29811@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]
There is a new pull request by UsernameRandomlyGenerated against master on the void-packages repository
https://github.com/UsernameRandomlyGenerated/void-packages python-pycodestyle
https://github.com/void-linux/void-packages/pull/29811
python-pycodestyle: update to 2.7.0.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
Needed for https://github.com/void-linux/void-packages/pull/29630
A patch file from https://github.com/void-linux/void-packages/pull/29811.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python-pycodestyle-29811.patch --]
[-- Type: text/x-diff, Size: 1431 bytes --]
From 308f5c970cecb6f9f6f93d1a975bc382e957c8da Mon Sep 17 00:00:00 2001
From: UsernameRandomlyGenerated <coredavid@tutanota.com>
Date: Sun, 28 Mar 2021 18:12:35 +0200
Subject: [PATCH] python-pycodestyle: update to 2.7.0.
---
srcpkgs/python-pycodestyle/template | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python-pycodestyle/template b/srcpkgs/python-pycodestyle/template
index 157a5d5f9fc1..c3de3b731620 100644
--- a/srcpkgs/python-pycodestyle/template
+++ b/srcpkgs/python-pycodestyle/template
@@ -1,19 +1,25 @@
# Template file for 'python-pycodestyle'
pkgname=python-pycodestyle
-version=2.6.0
-revision=3
+version=2.7.0
+revision=1
wrksrc="pycodestyle-${version}"
build_style=python-module
hostmakedepends="python-setuptools python3-setuptools"
depends="python-setuptools"
+checkdepends="python-pytest python3-pytest"
short_desc="Python2 style guide checker (formerly called pep8)"
maintainer="Alessio Sergi <al3hex@gmail.com>"
license="MIT"
homepage="https://github.com/PyCQA/pycodestyle"
distfiles="${PYPI_SITE}/p/pycodestyle/pycodestyle-${version}.tar.gz"
-checksum=c58a7d2815e0e8d7972bf1803331fb0152f867bd89adf8a01dfd55085434192e
+checksum=c389c1d06bf7904078ca03399a4816f974a1d590090fecea0c63ec26ebaf1cef
alternatives="pycodestyle:pycodestyle:/usr/bin/pycodestyle2"
+do_check() {
+ python -m pytest
+ python3 -m pytest
+}
+
post_install() {
vlicense LICENSE
}
next reply other threads:[~2021-03-28 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 16:13 UsernameRandomlyGenerated [this message]
2021-03-29 16:28 ` Chocimier
2021-03-29 16:28 ` [PR PATCH] [Closed]: " Chocimier
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29811@inbox.vuxu.org \
--to=usernamerandomlygenerated@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).