From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] flake8: update to 3.9.2
Date: Mon, 12 Jul 2021 23:28:50 +0200 [thread overview]
Message-ID: <20210712212850.e8Q-dY2iFee71KQU-Ec_RTXlMwBgGEQCxhAxjeluQAw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30973@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
New review comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/30973#discussion_r668269401
Comment:
https://flake8.pycqa.org/en/latest/faq.html#why-does-flake8-use-ranges-for-its-dependencies
> Flake8 uses ranges for mccabe, pyflakes, and pycodestyle because each of those projects tend to add new checks in minor releases. It has been an implicit design goal of Flake8’s to make the list of error codes stable in its own minor releases. That way if you install something from the 2.5 series today, you will not find new checks in the same series in a month from now when you install it again.
It seems like the version restrictions are not really necessary on void, I removed them.
next prev parent reply other threads:[~2021-07-12 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 21:16 [PR PATCH] " paper42
2021-05-19 23:20 ` ericonr
2021-05-20 7:12 ` [PR PATCH] [Updated] " paper42
2021-05-20 7:19 ` paper42
2021-05-21 15:23 ` [PR PATCH] [Updated] " paper42
2021-05-21 15:26 ` paper42
2021-07-05 20:24 ` [PR PATCH] [Updated] " paper42
2021-07-05 20:33 ` paper42
2021-07-12 19:26 ` [PR REVIEW] " ericonr
2021-07-12 21:27 ` [PR PATCH] [Updated] " paper42
2021-07-12 21:28 ` paper42 [this message]
2021-07-14 14:39 ` [PR PATCH] [Merged]: " ericonr
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=20210712212850.e8Q-dY2iFee71KQU-Ec_RTXlMwBgGEQCxhAxjeluQAw@z \
--to=paper42@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).