A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-September/103498.html below:

[Python-Dev] [Python-checkins] r84559 - python/branches/py3k/Lib/subprocess.py

[Python-Dev] [Python-checkins] r84559 - python/branches/py3k/Lib/subprocess.py [Python-Dev] [Python-checkins] r84559 - python/branches/py3k/Lib/subprocess.pyNick Coghlan ncoghlan at gmail.com
Tue Sep 7 15:19:47 CEST 2010
On Tue, Sep 7, 2010 at 11:05 PM, Brian Curtin <brian.curtin at gmail.com> wrote:
> Sure, seems reasonable to me.
> Does """raise ValueError("Unsupported signal: {}".format(sig))""" look fine,
> or is there a more preferred format when displaying bad values in exception
> messages?

No, that's about what I was thinking as well. When all we have is an
error code (or similar number), it's difficult to make the associated
error message particularly pretty.

Cheers,
Nick.


-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4