Remove redundant calls to list()

Unsafe listification of weakref in Python < 2.7.4

- sessions are now shared between series.
- use site data dir instead of user data dir if user has no home dir.
- in http and module handling, `data-dir` was used before being
initialized, using the default value instead of user input

(fixes #308, #904)

[REM] models: remove the magic methods signal_XXX()

Fixes #971:

File "/Users/keje/src/odoo/addons/account/partner.py", line 107, in get_fiscal_position
    return part.property_account_position.id
NameError: global name 'part' is not defined

[FIX]menu bar: clean up css and few cosmetics

(Manual rebase of #956, pending update in Launchpad translations)

* 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)

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

Raise exception when a DB request fetches ids it was not asked for

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

(Rebase of PR #883)

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

Fix implicit globals in kanban_gauge JS

A squashed merge is required as the conversion of the apiculture branch from
bzr to git was not correctly done. The git history contains irrelevant blobs
and commits. This branch brings a lot of changes and fixes, too many to list
exhaustively.

- New orm api, objects are now used instead of ids
- Environements to encapsulates cr uid context while maintaining backward compatibility
- Field compute attribute is a new object oriented way to define function fields
- Shared browse record cache
- New onchange protocol
- Optional copy flag on fields
- Documentation update
- Dead code cleanup
- Lots of fixes

(Manual rebase of PR #915)

(Manual rebase of PR #913)

Mixes the mass_mailing_id and mass_mailing_campaign_id
between the two models. Introduced by 9fc4ad99, PR #472

This instance was not actually exploitable for
SQL injection as it is not callable directly
via RPC and guarded by other queries when indirectly
called. Still plain awful.

This instance was not actually exploitable for
SQL injection as it is not callable directly
via RPC and guarded by other queries when indirectly
called. Still plain awful.

[REV] Partial revert of search view changes: indeed the graph view is not already capable of handling group_by on any field, declaring them is still necessary.

Fixes issue #911

[IMP] account: added a button on bank statements to see the journal items created as soon as some are created

[FIX] web_kanban_sparkline, sales_team, stock: use char function field to transmit sparkline data; the data is now correctly dumped into json, and parsed in the widget.

Replace NIH concat function

The installation of a multilang localisation (e.g. Belgium) used to install as well account_accountant (and then account_voucher) for no technical reason and was considered as the full accounting package.

[IMP] account, account_cancel: added the possibility to cancel a single statement line when it has already been through the reconciliation process