Code

Opened 3 years ago

Closed 3 years ago

#15635 closed (fixed)

New-style raise in documentation

Reported by: DaNmarner Owned by: DaNmarner
Component: Uncategorized Version: master
Severity: Keywords: PEP8
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

This is a follow-up patch to ticket #15609. It fixes the raise style in the documentation as well as an appearance in /django/utils/unittest/case.py

Attachments (2)

new_style_raise_in_docs.patch (6.4 KB) - added by DaNmarner 3 years ago.
3rd_style_patch.patch (1.9 KB) - added by DaNmarner 3 years ago.

Download all attachments as: .zip

Change History (8)

Changed 3 years ago by DaNmarner

comment:1 Changed 3 years ago by ramiro

In [15874]:

Changed 'raise' statements to new style syntax in documentation. Thanks DaNmarner. Refs #15635.

comment:2 Changed 3 years ago by DaNmarner

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to fixed
  • Status changed from new to closed

comment:3 Changed 3 years ago by DaNmarner

  • Resolution fixed deleted
  • Status changed from closed to reopened

Changed 3 years ago by DaNmarner

comment:4 Changed 3 years ago by DaNmarner

  • Status changed from reopened to new

Either my regex skill or Emacs failed me. Anyway, I found two more of these old style raise.

comment:5 Changed 3 years ago by julien

  • Triage Stage changed from Unreviewed to Ready for checkin

3rd_style_patch.patch is the patch to apply.

comment:6 Changed 3 years ago by adrian

  • Resolution set to fixed
  • Status changed from new to closed

In [15917]:

Fixed #15635 -- Converted two legacy old-style raise statements. Thanks, DaNmarner

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.