[NOIMP] Create move before other move when routing location is different from production source location
[IMP] Corrections in views + calendar fields isinstance + inventory theoretical qty
[MERGE] Merge from master routing conflict
[FIX] Take into account that location_id of routing can be empty
Merge remote-tracking branch 'odoo/master' into master-wmsstaging4-jco
[IMP] Update views and production_delay and track_production should go to product_template
[IMP] Try to solve BoM expansion + check for context for splitting/copying moves
[IMP] Adapt views of product template start
[FIX] website_sale: discount price is never hide
skip the inactivate employee in leaves summary
[FIX]Display answers in order by posted date in descending (latest to old)
[IMP] raise exception when a DB request fetches ids it was not asked for

Likely caused by a type incoherence e.g. providing an id as string when the
table uses integer ids. Postgres performs an implicit conversion from string
to integer[0], this wasn't much of an issue in the old API, whatever cache was
there would simply not be used, but because the new API's cache is part of its
behavior it has a semantic impact and can lead to infinite recursion.

[0] more precisely from quoted value, which is untyped
Update holidays_summary_report.py

Add context to search method
[REM] models: remove the magic methods signal_XXX()
Update holidays_summary_report.py
[FIX] signal_XXX -> signal_workflow: forgot quotes around signal name
[I18N] sale: fix pt translations

"Ordem de Vendas" changed to "Ordem de Venda"

(Rebase of PR #883)
Merge pull request #967 from xmo-odoo/master-id-type-xmo

Raise exception when a DB request fetches ids it was not asked for
[FIX] unsafe listification of weakref in Python < 2.7.4

Fixes #966

* As a preallocation optimization, ``list()`` calls ``__len__`` on its
  parameter if it's available
* Before Python 2.7.4, WeakSet has a bug[0] where ``len()`` is unsafe: it is
  done by iteration and weakrefs may be removed from the underlying set during
  the iteration

As a result, the safety feature of listifying a WeakSet to ensure we have
strong refs on all items during iteration may blow up.

Wrapping the weakset in a ``iter()`` makes ``__len__()`` invisible and ensures
we're within the IterationGuard[1].

Which now that I think about it means we *should* be able to safely iterate
weaksets in the first place and may not have needed to listify them...

[0] http://bugs.python.org/issue14159
[1] http://hg.python.org/cpython/file/b6acfbe2bdbe/Lib/_weakrefset.py#l58
[REM] unecessary calls to list()

* Either further operations don't really care (e.g. ``str.join`` takes any
  iterable)
* Or they do their own seq (``browse`` calls ``tuple()`` on iterable params)