[Django] #28427: Setup.py uses old % formatting

3 views
Skip to first unread message

Django

unread,
Jul 21, 2017, 3:33:13 PM7/21/17
to django-...@googlegroups.com
#28427: Setup.py uses old % formatting
------------------------------------------------+------------------------
Reporter: Joseph Bywater | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Packaging | Version: 1.11
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
------------------------------------------------+------------------------
The setup.py file uses the old % form of formatting strings rather than
the newer, better way of using the format function `string.format()`
Although it is not causing any issues, I believe that it should be updated
to be more modern.

Is this intentional or has it just not needed to be changed so it hasn't
been?

--
Ticket URL: <https://code.djangoproject.com/ticket/28427>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jul 21, 2017, 3:34:17 PM7/21/17
to django-...@googlegroups.com
#28427: Setup.py uses old % formatting
-------------------------------------+-------------------------------------

Reporter: Joseph Bywater | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Packaging | Version: 1.11
Severity: Normal | Resolution:

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by Joseph Bywater:

Old description:

> The setup.py file uses the old % form of formatting strings rather than
> the newer, better way of using the format function `string.format()`
> Although it is not causing any issues, I believe that it should be
> updated to be more modern.
>
> Is this intentional or has it just not needed to be changed so it hasn't
> been?

New description:

The setup.py file uses the old % form of formatting strings rather than
the newer, better way of using the format function `string.format()`
Although it is not causing any issues, I believe that it should be updated
to be more modern.

This issue is on line 91.

Is this intentional (for compatibility) or has it just not needed to be


changed so it hasn't been?

--

--
Ticket URL: <https://code.djangoproject.com/ticket/28427#comment:1>

Django

unread,
Jul 21, 2017, 3:37:16 PM7/21/17
to django-...@googlegroups.com
#28427: Setup.py uses old % formatting
-------------------------------------+-------------------------------------

Reporter: Joseph Bywater | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Error reporting | Version: 1.11
Severity: Normal | Resolution:

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Joseph Bywater):

* component: Packaging => Error reporting


--
Ticket URL: <https://code.djangoproject.com/ticket/28427#comment:2>

Django

unread,
Jul 21, 2017, 3:59:59 PM7/21/17
to django-...@googlegroups.com
#28427: Setup.py uses old % formatting
-------------------------------------+-------------------------------------

Reporter: Joseph Bywater | Owner: nobody
Type: | Status: closed

Cleanup/optimization |
Component: Error reporting | Version: 1.11
Severity: Normal | Resolution: wontfix

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz):

* status: new => closed
* resolution: => wontfix


Comment:

Thanks for the report, but I think we already discussed this and found no
compelling reason to move to the `format()` syntax everywhere.

--
Ticket URL: <https://code.djangoproject.com/ticket/28427#comment:3>

Reply all
Reply to author
Forward
0 new messages