Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#22820 closed Bug (fixed)

lazy_number raise KeyError if number is long type (python 2.7)

Reported by: Vitaliy Yelnik Owned by: nobody
Component: Translations Version: 1.6
Severity: Normal Keywords: translation lazy_number
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: yes Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

lazy_number raise KeyError in python 2.7 if number is long type.

Patch: ​https://github.com/django/django/pull/2801

Change History (5)

comment:1 by Vitaliy Yelnik, 10 years ago

Summary: lazy_number for python 2.7 fail → lazy_number raise KeyError if number is long type (python 2.7)

comment:2 by Tim Graham, 10 years ago

Needs tests: set
Triage Stage: Unreviewed → Accepted

Can you add a test?

comment:3 by Vitaliy Yelnik, 10 years ago

See also https://code.djangoproject.com/ticket/22840

Last edited 10 years ago by Vitaliy Yelnik (previous) (diff)

comment:4 by Claude Paroz <claude@…>, 10 years ago

Resolution: → fixed
Status: new → closed

In 502142179996e32e1c7f334c3d986f21115cfac8:

Fixed #22820 -- Treated int and long types alike in lazy_number

Thanks kwist for the report and the initial patch.

comment:5 by Claude Paroz <claude@…>, 10 years ago

In d839c756645b5091d55f67bbc4ff10718ff61a6b:

[1.7.x] Fixed #22820 -- Treated int and long types alike in lazy_number

Thanks kwist for the report and the initial patch.
Backport of 5021421799 from master.

Note: See TracTickets for help on using tickets.
Back to Top