zhulingjie 1984fb4136 Update json module to jsonutils

1. oslo project provide jsonutils, and barbican use it in many place[1],
this PS to update the remained json moudule to oslo jsonutils for
consistency.
2. update the primary jsonutils to use alias json

[1]: https://github.com/openstack/barbican/search?utf8=%E2%9C%93&q=jsonutils&type=

Change-Id: I958a711db17bb1aa86fc4cd23c00cec185b84ab2

2019-03-07 07:02:48 +00:00

2.8 KiB

Raw Blame History

Barbican Style Commandments

Step 1: Read the OpenStack Style Commandments https://docs.openstack.org/hacking/latest/
Step 2: Read on

Barbican Specific Commandments

[B310] Check for improper use of logging format arguments.
[B311] Use assertIsNone(...) instead of assertEqual(None, ...).
[B312] Use assertTrue(...) rather than assertEqual(True, ...).
[B314] str() and unicode() cannot be used on an exception. Remove or use six.text_type().
[B317] oslo_ should be used instead of oslo.
[B318] Must use a dict comprehension instead of a dict constructor with a sequence of key-value pairs.
[B319] Ensure to not use xrange().
[B320] Do not use LOG.warn as it's deprecated.
[B321] Use assertIsNotNone(...) rather than assertNotEqual(None, ...) or assertIsNot(None, ...).

Creating Unit Tests

For every new feature, unit tests should be created that both test and (implicitly) document the usage of said feature. If submitting a patch for a bug that had no unit test, a new passing unit test should be added. If a submitted bug fix does have a unit test, be sure to add a new one that fails without the patch and passes with the patch.

Running Tests

The testing system is based on a combination of tox and testr. If you just want to run the whole suite, run tox and all will be fine. However, if you'd like to dig in a bit more, you might want to learn some things about testr itself. A basic walkthrough for OpenStack can be found at http://wiki.openstack.org/testr

OpenStack Trademark

OpenStack is a registered trademark of OpenStack, LLC, and uses the following capitalization:

OpenStack

Commit Messages

Using a common format for commit messages will help keep our git history readable. Follow these guidelines:

First, provide a brief summary (it is recommended to keep the commit title under 50 chars).

The first line of the commit message should provide an accurate description of the change, not just a reference to a bug or blueprint. It must be followed by a single blank line.

Following your brief summary, provide a more detailed description of the patch, manually wrapping the text at 72 characters. This description should provide enough detail that one does not have to refer to external resources to determine its high-level functionality.

Once you use 'git review', two lines will be appended to the commit message: a blank line followed by a 'Change-Id'. This is important to correlate this commit with a specific review in Gerrit, and it should not be modified.

For further information on constructing high quality commit messages, and how to split up commits into a series of changes, consult the project wiki:

http://wiki.openstack.org/GitCommitMessages

2.8 KiB Raw Blame History