openstack
/
neutron
Code Issues Proposed changes
OpenStack Networking (Neutron)
7,172 Commits 9 Branches 73 Tags 1,009 MiB
Python 99.5%
Shell 0.4%
Jinja 0.1%
Go to file
Angus Lees f16101d711 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
bin Remove the useless vim modelines 2014-06-21 15:07:31 +08:00
doc Implement ModelsMigrationsSync test from oslo.db 2014-09-30 11:55:06 +04:00
etc openvswitch: Remove no longer used options 2014-10-15 14:05:15 +09:00
neutron Remove single occurrence of lost-exception warning 2014-10-20 10:12:39 +11:00
rally-scenarios Add config for performance gate job 2014-06-26 14:27:15 +03:00
tools Remove the useless vim modelines 2014-06-21 15:07:31 +08:00
.coveragerc fix some missing change from quantum to neutron 2013-07-08 12:11:04 +08:00
.gitignore Ignore emacs checkpoint files 2014-06-18 13:48:41 -05:00
.gitreview Rename quantum to neutron in .gitreview. 2013-07-06 12:25:09 -04:00
.mailmap Add mailmap entry 2014-05-16 13:40:04 -04:00
.pylintrc Remove single occurrence of lost-exception warning 2014-10-20 10:12:39 +11:00
.testr.conf Add an explicit tox job for functional tests 2014-02-05 17:11:52 +00:00
CONTRIBUTING.rst Add CONTRIBUTING.rst 2014-07-08 23:49:07 +08:00
HACKING.rst Remove @author(s) from copyright statements 2014-09-15 21:40:09 +09:00
LICENSE Adding Apache Version 2.0 license file. This is the official license agreement under which Quantum code is available to 2011-08-08 12:31:04 -07:00
MANIFEST.in Rename Quantum to Neutron 2013-07-06 15:02:43 -04:00
README.rst Make readme reference git.openstack.org not github 2014-07-17 10:57:12 +02:00
TESTING.rst Merge "Add a gate-specific tox env for functional tests" 2014-07-19 02:48:16 +00:00
babel.cfg Use babel to generate translation file 2013-01-24 00:20:32 +08:00
openstack-common.conf Remove sslutils from openstack.common 2014-10-07 11:16:49 +02:00
requirements.txt Updated from global requirements 2014-10-11 22:33:01 +00:00
run_tests.sh Provide a quick way to run flake8 2014-08-30 21:30:17 +09:00
setup.cfg Merge "Open Kilo development" 2014-10-02 17:19:42 +00:00
setup.py Updated from global requirements 2014-04-30 02:41:29 +00:00
test-requirements.txt Updated from global requirements 2014-10-11 22:33:01 +00:00
tox.ini Merge "Add pylint tox environment and disable all existing warnings" 2014-10-18 08:57:58 +00:00

README.rst

# -- Welcome!

You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!

# -- External Resources:

The homepage for Neutron is: http://launchpad.net/neutron. Use this site for asking for help, and filing bugs. Code is available on git.openstack.org at <http://git.openstack.org/cgit/openstack/neutron>.

The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:

Neutron Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/

Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/

The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment

For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.