1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
|
%global _empty_manifest_terminate_build 0
Name: python-flake8-length
Version: 0.3.1
Release: 1
Summary: Flake8 plugin for a smart line length validation.
License: MIT
URL: https://github.com/orsinium-labs/flake8-length
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/65/f9/8a80b7caf5637ff74ae9b0666e2f130a2493b6a325ec6b41dd2159b65d60/flake8-length-0.3.1.tar.gz
BuildArch: noarch
Requires: python3-flake8
Requires: python3-isort
Requires: python3-mypy
Requires: python3-pytest
%description
# flake8-length
[Flake8](https://gitlab.com/pycqa/flake8) plugin for a smart line length validation.
[pycodestyle](https://github.com/PyCQA/pycodestyle) linter (used in Flake8 under the hood by default) already has `E501` and `W505` rules to validate the line length. flake8-length provides an alternative check that is smarter and more forgiving.
What is allowed:
+ Long string literals.
+ Long URLs in strings and comments.
+ When the last word in a text doesn't fit a bit.
## Motivation
From [linux code style](https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst#2-breaking-long-lines-and-strings):
> Statements longer than 80 columns will be broken into sensible chunks, unless exceeding 80 columns significantly increases readability and does not hide information. <...> However, never break user-visible strings such as printk messages, because that breaks the ability to grep for them.
I see a lot of Python code that does some awful breaks to fit long text messages into the project's line limit just because. However, it creates a lot of difficulties:
1. Difficult to grep.
1. Easy to miss a space on the string breaks.
1. It doesn't make code more readable at all, even decreases readability. In most cases, I don't care if the ending of an error message goes outside of my screen.
Some modern languages even don't have this limitation:
> Go has no line length limit. Don't worry about overflowing a punched card.
However, it makes sense to keep some limit to guide developers and keep the alignment reasonable.
[Uncle Bob analyzed line length in some popular Java project](https://youtu.be/2a_ytyt9sf8?t=2792). The conclusion is it is usually about 45 on average, more than 97 is too much and exceptional.
[Raymond Hettinger advises to keep it 90ish](https://youtu.be/wf-BqAjZb8M?t=260). The limit should be about 90 but with reasonable exceptions for when breaking the line would negatively affect the readability.
[Kevlin Henney says even 80 is too generous](https://youtu.be/ZsHMHukIlJY?t=716). People read the code following one up-down flow, and breaking the flow with long lines makes the code harder to read.
If you ever had to break a text message to fit in the limit, you know why the plugin exists.
If you're about having as strict limits as possible, flake8-length is on your side. It's better to set 90 chars limit with a few reasonable exceptions rather than have 120 or more chars limit for everything.
## Installation
Install:
```bash
python3 -m pip install --user flake8-length
```
And check if the plugin is detected by flake8:
```bash
flake8 --version
```
If it doesn't, flake8-length was installed in another python interpreter rather than flake8. You can find the right one:
```bash
head -1 $(which flake8)
```
## Usage
+ If you're installed flake8-length and flake8 in the same environment, when you run flake8 it will run the plugin. Just give it a try.
+ pycodestyle has a few hard limits on lime length (`E501` and `W505`), so these checks should be disabled to avoid conflicts with flake8-length.
+ The default soft limit is set using [max-line-length](https://flake8.pycqa.org/en/latest/user/options.html#cmdoption-flake8-max-line-length) option. It is 79 by default.
Configuration example (`setup.cfg`):
```ini
[flake8]
extend-ignore =
E501,
W505
max-line-length = 90
```
What the limit you should use? I'd say, as small as possible. Try to start with the default one (79) and if you feel it's not enough, extend it to 90. More is too generous.
%package -n python3-flake8-length
Summary: Flake8 plugin for a smart line length validation.
Provides: python-flake8-length
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-flake8-length
# flake8-length
[Flake8](https://gitlab.com/pycqa/flake8) plugin for a smart line length validation.
[pycodestyle](https://github.com/PyCQA/pycodestyle) linter (used in Flake8 under the hood by default) already has `E501` and `W505` rules to validate the line length. flake8-length provides an alternative check that is smarter and more forgiving.
What is allowed:
+ Long string literals.
+ Long URLs in strings and comments.
+ When the last word in a text doesn't fit a bit.
## Motivation
From [linux code style](https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst#2-breaking-long-lines-and-strings):
> Statements longer than 80 columns will be broken into sensible chunks, unless exceeding 80 columns significantly increases readability and does not hide information. <...> However, never break user-visible strings such as printk messages, because that breaks the ability to grep for them.
I see a lot of Python code that does some awful breaks to fit long text messages into the project's line limit just because. However, it creates a lot of difficulties:
1. Difficult to grep.
1. Easy to miss a space on the string breaks.
1. It doesn't make code more readable at all, even decreases readability. In most cases, I don't care if the ending of an error message goes outside of my screen.
Some modern languages even don't have this limitation:
> Go has no line length limit. Don't worry about overflowing a punched card.
However, it makes sense to keep some limit to guide developers and keep the alignment reasonable.
[Uncle Bob analyzed line length in some popular Java project](https://youtu.be/2a_ytyt9sf8?t=2792). The conclusion is it is usually about 45 on average, more than 97 is too much and exceptional.
[Raymond Hettinger advises to keep it 90ish](https://youtu.be/wf-BqAjZb8M?t=260). The limit should be about 90 but with reasonable exceptions for when breaking the line would negatively affect the readability.
[Kevlin Henney says even 80 is too generous](https://youtu.be/ZsHMHukIlJY?t=716). People read the code following one up-down flow, and breaking the flow with long lines makes the code harder to read.
If you ever had to break a text message to fit in the limit, you know why the plugin exists.
If you're about having as strict limits as possible, flake8-length is on your side. It's better to set 90 chars limit with a few reasonable exceptions rather than have 120 or more chars limit for everything.
## Installation
Install:
```bash
python3 -m pip install --user flake8-length
```
And check if the plugin is detected by flake8:
```bash
flake8 --version
```
If it doesn't, flake8-length was installed in another python interpreter rather than flake8. You can find the right one:
```bash
head -1 $(which flake8)
```
## Usage
+ If you're installed flake8-length and flake8 in the same environment, when you run flake8 it will run the plugin. Just give it a try.
+ pycodestyle has a few hard limits on lime length (`E501` and `W505`), so these checks should be disabled to avoid conflicts with flake8-length.
+ The default soft limit is set using [max-line-length](https://flake8.pycqa.org/en/latest/user/options.html#cmdoption-flake8-max-line-length) option. It is 79 by default.
Configuration example (`setup.cfg`):
```ini
[flake8]
extend-ignore =
E501,
W505
max-line-length = 90
```
What the limit you should use? I'd say, as small as possible. Try to start with the default one (79) and if you feel it's not enough, extend it to 90. More is too generous.
%package help
Summary: Development documents and examples for flake8-length
Provides: python3-flake8-length-doc
%description help
# flake8-length
[Flake8](https://gitlab.com/pycqa/flake8) plugin for a smart line length validation.
[pycodestyle](https://github.com/PyCQA/pycodestyle) linter (used in Flake8 under the hood by default) already has `E501` and `W505` rules to validate the line length. flake8-length provides an alternative check that is smarter and more forgiving.
What is allowed:
+ Long string literals.
+ Long URLs in strings and comments.
+ When the last word in a text doesn't fit a bit.
## Motivation
From [linux code style](https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst#2-breaking-long-lines-and-strings):
> Statements longer than 80 columns will be broken into sensible chunks, unless exceeding 80 columns significantly increases readability and does not hide information. <...> However, never break user-visible strings such as printk messages, because that breaks the ability to grep for them.
I see a lot of Python code that does some awful breaks to fit long text messages into the project's line limit just because. However, it creates a lot of difficulties:
1. Difficult to grep.
1. Easy to miss a space on the string breaks.
1. It doesn't make code more readable at all, even decreases readability. In most cases, I don't care if the ending of an error message goes outside of my screen.
Some modern languages even don't have this limitation:
> Go has no line length limit. Don't worry about overflowing a punched card.
However, it makes sense to keep some limit to guide developers and keep the alignment reasonable.
[Uncle Bob analyzed line length in some popular Java project](https://youtu.be/2a_ytyt9sf8?t=2792). The conclusion is it is usually about 45 on average, more than 97 is too much and exceptional.
[Raymond Hettinger advises to keep it 90ish](https://youtu.be/wf-BqAjZb8M?t=260). The limit should be about 90 but with reasonable exceptions for when breaking the line would negatively affect the readability.
[Kevlin Henney says even 80 is too generous](https://youtu.be/ZsHMHukIlJY?t=716). People read the code following one up-down flow, and breaking the flow with long lines makes the code harder to read.
If you ever had to break a text message to fit in the limit, you know why the plugin exists.
If you're about having as strict limits as possible, flake8-length is on your side. It's better to set 90 chars limit with a few reasonable exceptions rather than have 120 or more chars limit for everything.
## Installation
Install:
```bash
python3 -m pip install --user flake8-length
```
And check if the plugin is detected by flake8:
```bash
flake8 --version
```
If it doesn't, flake8-length was installed in another python interpreter rather than flake8. You can find the right one:
```bash
head -1 $(which flake8)
```
## Usage
+ If you're installed flake8-length and flake8 in the same environment, when you run flake8 it will run the plugin. Just give it a try.
+ pycodestyle has a few hard limits on lime length (`E501` and `W505`), so these checks should be disabled to avoid conflicts with flake8-length.
+ The default soft limit is set using [max-line-length](https://flake8.pycqa.org/en/latest/user/options.html#cmdoption-flake8-max-line-length) option. It is 79 by default.
Configuration example (`setup.cfg`):
```ini
[flake8]
extend-ignore =
E501,
W505
max-line-length = 90
```
What the limit you should use? I'd say, as small as possible. Try to start with the default one (79) and if you feel it's not enough, extend it to 90. More is too generous.
%prep
%autosetup -n flake8-length-0.3.1
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-flake8-length -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 0.3.1-1
- Package Spec generated
|
