[issue14306] try/except block is both efficient and expensive?

2012-03-17 Thread Roundup Robot

Roundup Robot devn...@psf.upfronthosting.co.za added the comment:

New changeset 9a7dcfbcf726 by Georg Brandl in branch '3.2':
Closes #14306: clarify expensiveness of try-except and update code snippet
http://hg.python.org/cpython/rev/9a7dcfbcf726

--
nosy: +python-dev
resolution:  - fixed
stage:  - committed/rejected
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14306
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue14306] try/except block is both efficient and expensive?

2012-03-17 Thread Roundup Robot

Roundup Robot devn...@psf.upfronthosting.co.za added the comment:

New changeset 7a93f6ee2ebc by Georg Brandl in branch '2.7':
Closes #14306: clarify expensiveness of try-except and update code snippet
http://hg.python.org/cpython/rev/7a93f6ee2ebc

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14306
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue14306] try/except block is both efficient and expensive?

2012-03-16 Thread Terry J. Reedy

Terry J. Reedy tjre...@udel.edu added the comment:

I think it would be sufficient to add ' if no exceptions are raised' to the 
first sentence. The example that follows in the entry clarifies the 
implications of cheap to try, expensive to catch.

--
keywords: +patch
nosy: +terry.reedy

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14306
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue14306] try/except block is both efficient and expensive?

2012-03-14 Thread Tshepang Lekhonkhobe

New submission from Tshepang Lekhonkhobe tshep...@gmail.com:

In Doc/faq/design.rst, we got this text:

A try/except block is extremely efficient. Actually catching an exception is 
expensive.

The 2 sentences appear contradictory.

--
assignee: docs@python
components: Documentation
messages: 155798
nosy: docs@python, tshepang
priority: normal
severity: normal
status: open
title: try/except block is both efficient and expensive?

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14306
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue14306] try/except block is both efficient and expensive?

2012-03-14 Thread Georg Brandl

Georg Brandl ge...@python.org added the comment:

It could be reworded, yes.

--
nosy: +georg.brandl

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14306
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue14306] try/except block is both efficient and expensive?

2012-03-14 Thread Ezio Melotti

Ezio Melotti ezio.melo...@gmail.com added the comment:

What it's trying to say is that in case the operation in the try block 
succeeds there's almost no overhead, so it's very efficient.  On the other 
hand, raising and then catching the error is expensive.

--
nosy: +ezio.melotti

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14306
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com