In some fonts, character 'l' are indistinguishable from the numeral one.
So better use other name instead.
https://github.com/django/django/blob/master/tests/queries/tests.py#L567&L574
--
Ticket URL: <https://code.djangoproject.com/ticket/27463>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* owner: nobody => Ramin Farajpour Cami
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:1>
Comment (by Ramin Farajpour Cami):
https://pep8.readthedocs.io/en/latest/_modules/pycodestyle.html
{{{
Okay: L = 0
Okay: o = 123
Okay: i = 42
E741: l = 0
E741: O = 123
E741: I = 42
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:2>
* component: Utilities => Core (Other)
Comment:
I'm not sure about this, particularly if our style tool (`flake8`) doesn't
provide automated enforcement. A font that doesn't distinguish between one
character or another doesn't seem so useful for programmers.
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:3>
Comment (by Ramin Farajpour Cami):
really!
Flake8 uses ranges for mccabe, pyflakes, and pycodestyle because each of
those projects tend to add new checks in minor releases.
http://flake8.pycqa.org/en/latest/faq.html#why-does-flake8-use-ranges-for-
its-dependencies
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:4>
Comment (by Ramin Farajpour Cami):
pycodestyle member tell me :
https://github.com/PyCQA/pycodestyle/issues/598
Allow me for PR ?
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:5>
Comment (by Aymeric Augustin):
I have yet to come across a monospace font where `l` and `I` are
identical, but it takes less effort to accept a PR making that change than
to discuss.
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:6>
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:7>
Comment (by Ramin Farajpour Cami):
Hi,
i should check `ALL` files `.py` django for check this warnings?
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:8>
Comment (by Tim Graham):
Ideally you could get flake8 working with the latest version of
pycodestyle so you can see and fix all the warnings. If it's difficult,
then we'll just wait until flake8 is updated.
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:9>
Comment (by Ramin Farajpour Cami):
Ok, let's go , i need just `pycodesyle` latest version,
{{{
root@raminfp:~# python pycodestyle.py usr/django/django/apps
/usr/django/django/apps/registry.py:425:1: E305 expected 2 blank lines
after class or function definition, found 1
}}}
i going to fix `E305 expected 2 blank lines after class or function
definition, found 1`, because i see pycodestyle in new version,
Thanks Again,
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:10>
Comment (by Ramin Farajpour Cami):
[https://github.com/django/django/pull/7545 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:11>
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:12>
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:13>
* needs_better_patch: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:14>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:13>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"0a63ef3f61f42c5fd22f2d0b626e386fd426ebed" 0a63ef3f]:
{{{
#!CommitTicketReference repository=""
revision="0a63ef3f61f42c5fd22f2d0b626e386fd426ebed"
Fixed #27463 -- Fixed E741 flake8 warnings.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27463#comment:14>