[issue11884] Argparse calls ngettext but doesn't import it

John O'Hagan added the comment: Reported to Debian, bug #624277 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue11884] Argparse calls ngettext but doesn't import it

Éric Araujo added the comment: Confirmed. It’s a Debian-specific problem, please use “reportbug python3.2” to report it to them. -- nosy: +doko resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue11884] Argparse calls ngettext but doesn't import it

John O'Hagan added the comment: It's argparse version 1.1 (1.1-1) from current Debian testing, Python 3.2 (r32:88445, Feb 20 2011, 18:43:30) -- ___ Python tracker ___ _

[issue11884] Argparse calls ngettext but doesn't import it

Éric Araujo added the comment: I added the import and calls in 1827a8ac9b18, so this report is strange. What is your exact version and where did you get it? -- assignee: -> eric.araujo nosy: +eric.araujo ___ Python tracker

[issue11884] Argparse calls ngettext but doesn't import it

Changes by Ned Deily : -- nosy: +bethard ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue11884] Argparse calls ngettext but doesn't import it

New submission from John O'Hagan : Argparse in python3.2 includes two calls to ngettext to handle error messages, but ngettext is not imported. This causes NameError to be raised instead of ArgumentError. Changing line 93 from: from gettext import gettext to: from gettext import get