Angus Lees fe57eb2bff Remove single occurrence of lost-exception warning ... Returning within a finally block can be surprising since the finally block will "hijack" the regular return flow. In this case, pylint is trying to warn us that the return-within-finally would discard the earlier caught exception. For this particular function we don't care that the exception is lost, so the existing code is correct but possibly confusing. Our options are: 1. Disable the lost-exception warning for this function 2. Rewrite the function to avoid return-within-finally This change takes approach (2), since the required change is trivial. This change also enables the corresponding pylint check now that the only offending case has been removed. Change-Id: If1706851b4bd67ebdbbdb3485984773598efdf7a		2014-10-20 10:12:39 +11:00
..
__init__.py	Remove invalid copyright headers under API module	2014-04-02 11:09:03 -07:00
attributes.py	Remove single occurrence of lost-exception warning	2014-10-20 10:12:39 +11:00
base.py	Forbid regular users to reset admin-only attrs to default values	2014-09-23 15:18:51 +04:00
resource.py	Send HTTP exceptions in the format expected by neutronclient	2014-08-18 17:21:45 +04:00
resource_helper.py	Remove @author(s) from copyright statements	2014-09-15 21:40:09 +09:00
router.py	Use six.moves.urllib.parse instead of urlparse	2014-02-13 10:19:01 +08:00