The stdlib version of the json library is more recent than the 3.5.3
version we are pinning in `requirements.txt`

There is no reason to use it.

Closes #6940

The `unittest2` package is simply a backport of `unittest` from the
Standard Library of Python 2.7 to previous versions.

There is no reason to use it any longer.

Closes #6941

Modify test test_ir_values.py also, as the action was used in it.

The name_get has been updated accordingly : if an address has no name, we now show parent_name, res_partner.type.
The contact template shows the name when it exists, and the parent_name if it does not. This should produce cleaner reports.

Though the name field is no longer required on the res.partner model,
"required" attribute in views and an sql contraint enforce that all contacts have a name.

Read more / less feature is back (and probably ugly). It has probably been
removed when refactoring the old chatter.

[FIX] tools: html shortening: encoding issue

[FIX] orm, fields: read_group on monetary fields now correctly makes the sum instead of ignoring them

Don't need to add the empty value because ir_translation generate missing values automatically.
(bug e.g.: Link with empty string can't be clicked)

Not necessary anymore thanks to commit
731b9f60.

The test cursors were leaked by the _check_accounting_configured()
function used to manually skip some tests.

After 731b9f60 the tests are skipped cleanly without
leaking cursors, so this became redundant with the reset()
function already present in the TransactionCase cleanups.

This reverts commit 57b14988.

That would break a lot of methods (e.g. using formatLang method).
Closes #8659

In saas-6, the `ir_sequence_date` key in the context
has been introduced, to use this date instead of the
current date for sequences including date variables
(Year, month, day, ...).

So, when an invoice is created for a previous fiscal
year / period, the sequence is built according
to the date of this fiscal year / period.

e.g., for an invoice sequence containing the year,
for an invoice created in 2015, but which
is for the 2014 fiscal year, the sequence
contains 2014 instead of 2015.

Nevertheless, this leads to a retro-compatibility issue:
the impossibiliy to use the current date for your
invoices sequences.
Indeed, some users want to include the current month
and day in their invoices sequences,
e.g. xxx-20150922.

This revision brings the possibility to use both
possible dates, the beginning of the date range
or the current date.

opw-649487

The message used in 'valid_inheritance' was not very helpful when the
inheritance validity was not passed.
You only knew that some view was not OK without knowing which one.

We now use the 'raise_view_error' method, which can already display all
the meaningful info (view_id, parent_id, view name, ...)

Courtesy of Lionel Sausin

Fix traceback when a view had %()d or %()s
Now we replace it by the related id.

fix #8193

Since the new translation process for views, their arch is translated upon
reading the views, before applying inheritance.  Remove the useless translation
that was done after this process.

Specifically: audio, canvas, datalist, embed, iframe, map, object, select, svg,
template, textarea, video.

This avoids a few dumb queries.

Enable the prefetching of several fields while evaluating an onchange.  Special
care is taken to not prefetch computed fields or fields already in cache.  The
latter is necessary to avoid "cleaning up" dirty fields by accident.

The translations inside the i18n/ folder are the translations published on
Transifex. It will contains the translatable "general" terms (menus, error
messages, actions...).

The account, taxes, journal names are made translatable thanks to the
l10n_multlang module but it should only be translated in the `spoken_languages`
values (nl_BE for l10n_be). These translations are present in i18n_extra folder
which is not published on Transifex.

Regenerate the translations correctly and populate the nl_BE.po file with
previous translations.

Updating the field `arch` on `ir.ui.view` breaks when there is a language in
the context, since this is forbidden by the new translation scheme.

oups, forgot to reexport this one

If defined, use module_name, otherwise not doing much...
Courtesy of @KangOl

The "Synchronise translation" wizard almost doubles the number of translated
terms in database.
This is due to the loss of the module reference at the synchronisation
(`module_name` is empty as updating all modules)
Only overwrite the module when it is set (default None)
Fixes #6149

Second part of the patches avoid inserting translations without any module for
locale xml ids.

If an error happens in an overload of setUp, the already-open cursor
is likely not to get properly released before the next test,
deadlocking the db, because tearDown only runs if setUp has
succesfully completed.

Cleanups were added specifically to run every time, after tearDown has
(potentially) been executed.

closes #8327

Note: cleanups run in LIFO order (as they should).

NULL is too technical
Courtesy of Lionel Sausin