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
|
%global _empty_manifest_terminate_build 0
Name: python-flake8-variables-names
Version: 0.0.5
Release: 1
Summary: A flake8 extension that helps to make more readable variables names
License: MIT
URL: https://github.com/best-doctor/flake8-variables-names
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/80/a0/6c0a2fc99440a758b06a5c2b4af3931d521b9d2afba940e7a7adc8db9a47/flake8_variables_names-0.0.5.tar.gz
BuildArch: noarch
%description
# flake8-variables-names
[](https://github.com/best-doctor/flake8-variables-names/actions/workflows/build.yml)
[](https://codeclimate.com/github/best-doctor/flake8-variables-names/maintainability)
[](https://codeclimate.com/github/best-doctor/flake8-variables-names/test_coverage)
[](https://badge.fury.io/py/flake8-variables-names)
An extension for flake8 that helps to make more readable variables names.
We believe, that variable name should unmistakably shows, what it contains.
Thats why we try not to use varnames with only one symbol or not to use
too common names, such as `result`, `value` or `info`.
This extensions helps to detect such names. By default it works in
non-strict mode. You can change it with `--use-varnames-strict-mode`
parameter end extend variable names blacklist even more.
## Installation
```terminal
pip install flake8-variables-names
```
## Example
Sample file:
```python
# test.py
a = 1
foo = 2
result = a + foo
```
Usage:
```terminal
$ flake8 test.py
test.py:1:1: VNE001 single letter variable names are not allowed
test.py:2:1: VNE002 variable name should be clarified
```
## Error codes
| Error code | Description |
|:----------:|:-------------------------------------------------------:|
| VNE001 | single letter variable names like 'XXX' are not allowed |
| VNE002 | variable name 'XXX' should be clarified |
| VNE003 | variable names that shadow builtins are not allowed |
## Contributing
We would love you to contribute to our project. It's simple:
- Create an issue with bug you found or proposal you have.
Wait for approve from maintainer.
- Create a pull request. Make sure all checks are green.
- Fix review comments if any.
- Be awesome.
Here are useful tips:
- You can run all checks and tests with `make check`.
Please do it before CI does.
- We use [BestDoctor python styleguide](https://github.com/best-doctor/guides/blob/master/guides/en/python_styleguide.md).
- We respect [Django CoC](https://www.djangoproject.com/conduct/).
Make soft, not bullshit.
%package -n python3-flake8-variables-names
Summary: A flake8 extension that helps to make more readable variables names
Provides: python-flake8-variables-names
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-flake8-variables-names
# flake8-variables-names
[](https://github.com/best-doctor/flake8-variables-names/actions/workflows/build.yml)
[](https://codeclimate.com/github/best-doctor/flake8-variables-names/maintainability)
[](https://codeclimate.com/github/best-doctor/flake8-variables-names/test_coverage)
[](https://badge.fury.io/py/flake8-variables-names)
An extension for flake8 that helps to make more readable variables names.
We believe, that variable name should unmistakably shows, what it contains.
Thats why we try not to use varnames with only one symbol or not to use
too common names, such as `result`, `value` or `info`.
This extensions helps to detect such names. By default it works in
non-strict mode. You can change it with `--use-varnames-strict-mode`
parameter end extend variable names blacklist even more.
## Installation
```terminal
pip install flake8-variables-names
```
## Example
Sample file:
```python
# test.py
a = 1
foo = 2
result = a + foo
```
Usage:
```terminal
$ flake8 test.py
test.py:1:1: VNE001 single letter variable names are not allowed
test.py:2:1: VNE002 variable name should be clarified
```
## Error codes
| Error code | Description |
|:----------:|:-------------------------------------------------------:|
| VNE001 | single letter variable names like 'XXX' are not allowed |
| VNE002 | variable name 'XXX' should be clarified |
| VNE003 | variable names that shadow builtins are not allowed |
## Contributing
We would love you to contribute to our project. It's simple:
- Create an issue with bug you found or proposal you have.
Wait for approve from maintainer.
- Create a pull request. Make sure all checks are green.
- Fix review comments if any.
- Be awesome.
Here are useful tips:
- You can run all checks and tests with `make check`.
Please do it before CI does.
- We use [BestDoctor python styleguide](https://github.com/best-doctor/guides/blob/master/guides/en/python_styleguide.md).
- We respect [Django CoC](https://www.djangoproject.com/conduct/).
Make soft, not bullshit.
%package help
Summary: Development documents and examples for flake8-variables-names
Provides: python3-flake8-variables-names-doc
%description help
# flake8-variables-names
[](https://github.com/best-doctor/flake8-variables-names/actions/workflows/build.yml)
[](https://codeclimate.com/github/best-doctor/flake8-variables-names/maintainability)
[](https://codeclimate.com/github/best-doctor/flake8-variables-names/test_coverage)
[](https://badge.fury.io/py/flake8-variables-names)
An extension for flake8 that helps to make more readable variables names.
We believe, that variable name should unmistakably shows, what it contains.
Thats why we try not to use varnames with only one symbol or not to use
too common names, such as `result`, `value` or `info`.
This extensions helps to detect such names. By default it works in
non-strict mode. You can change it with `--use-varnames-strict-mode`
parameter end extend variable names blacklist even more.
## Installation
```terminal
pip install flake8-variables-names
```
## Example
Sample file:
```python
# test.py
a = 1
foo = 2
result = a + foo
```
Usage:
```terminal
$ flake8 test.py
test.py:1:1: VNE001 single letter variable names are not allowed
test.py:2:1: VNE002 variable name should be clarified
```
## Error codes
| Error code | Description |
|:----------:|:-------------------------------------------------------:|
| VNE001 | single letter variable names like 'XXX' are not allowed |
| VNE002 | variable name 'XXX' should be clarified |
| VNE003 | variable names that shadow builtins are not allowed |
## Contributing
We would love you to contribute to our project. It's simple:
- Create an issue with bug you found or proposal you have.
Wait for approve from maintainer.
- Create a pull request. Make sure all checks are green.
- Fix review comments if any.
- Be awesome.
Here are useful tips:
- You can run all checks and tests with `make check`.
Please do it before CI does.
- We use [BestDoctor python styleguide](https://github.com/best-doctor/guides/blob/master/guides/en/python_styleguide.md).
- We respect [Django CoC](https://www.djangoproject.com/conduct/).
Make soft, not bullshit.
%prep
%autosetup -n flake8-variables-names-0.0.5
%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-variables-names -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Sun Apr 23 2023 Python_Bot <Python_Bot@openeuler.org> - 0.0.5-1
- Package Spec generated
|
