[ADD] base_vat: add VAT validation for Peruvian localization.
[FIX] ir_fields: allow accent on selection import

If the selection label (not value) had accents, it wasn't possible to import it using the label having accents
[ADD] safe_eval: UNPACK_SEQUENCE and Exception

Allowing UNPACK_SEQUENCE allows the use of the "multi" assignation:
a, b = [1,2]
for a,b in items
[FIX] hr_holidays: do not allow reduce remaining leaves

In the Employee form, a remaining legal leaves field is available, which shows remaining validated leaves from allocation requests
As this is not allowed to delete a validated allocation requets, it shouldn't be possible to reduce the validated remaining leaves of an employee.
To reduce the remaining leaves of an employee, the user should cancel and remove the allocation request
[FIX] translate: Fix debug print when parse path list to translate.
[FIX] account: no journal items on consolidation accounts

As for the view accounts, the consolidation accounts should not allow to create journal items.
Fixes #1090
Revert 3dec090 "[FIX] ir_values: fallback when no condition"

An ir.value without condition should not match when searching with a condition.
When a field with change_default on it is modified, the method get_defaults is called with the new value. This means that manually modifying a field with this trigger would put back the default value (opw 611193).
[IMP] base_vat: differenciate VIES and classical VAT error

Display a different error message so that users are aware if the test failed with VIES enabled or not (opw 609823)
[FIX] web: on refresh, do search_read with fields passed
Merge pull request #1391 from savoirfairelinux/7.0-translate-trans_generate_debug_print

[FIX] translate: Fix debug print when parse path list to translate.
[FIX] mail: reset of default_type in context

When creating a new message, we need to reset the default_type key to avoid context propagation (e.g. invoice menu).
However we used to compare the key in context (char) with the list of selections (tuple) so it was never matching and always reset.
[FIX] stock: partial deliveries switch on delivered picking

Users don't care for the backorder picking precisely because they can't process it, whereas they may have to do some more things on the picking they processed: invoice it, print delivery orders or transportation stickers..
Refresh the browse record after changing the name to avoid the need to rebrowse.
Fixes #1372
[FIX] sale: config, timesheet if module account_analytic_analysis

In Settings > Sales, the onchange_timesheet ensure that if you check timesheet, it checks module_account_analytic_analysis.

Therefore, if module_account_analytic_analysis is installed, timesheet should be checked by default
Until now, it worked "luckily", because the onchange_timesheet of the field module_account_analytic_analysis was triggered before the onchange_timesheet of the timesheet field. Nevertheless, we shouldn't trust the onchange calls order.
[FIX] account_voucher: avoid trying unreconcile a move twice

When we cancel a voucher, we may be trying to unlink a reconciliation that was already removed on another move (just looking at the version in cache). In such cases, the unlink would fail with traceback. opw 610287
[FIX] project_long_term: avoid bad duplication of phases

When we duplicate a project, the related phases need to be duplicated as well but keeping references between each other.
e.g. 'project 1' with 'phase A' follwed by 'phase B' should become 'project 1 (copy)' with 'phase A (copy)' followed by 'phase B (copy)'.
Fixing bug lp:1212860, opw 607062
Passed default type while creating document page category from document page
[FIX] sale: copy_quotation must propagate the context
[FIX] account: on_change_unit_amount do not reset uom to default
[FIX] account: unit arg of on_change_unit_amount can be False
[FIX] orm: set default before removing magic fields

When a record is created, the magic fields (id, create_date,...) are first removed from the vals as the user should not set a value for these.
However if a value for this is given in default value (e.g. defined in an ir.value), the creation would crash (sql error : column specified more than once) as the magic column would be added again.