[request/session] refactor language handling: don't attempt to sync web/repo languages
This decouple thing and make code easier to understand. Previous behaviour was fine
w/ validation error that were translated on the server side, but isn't satisfying for
notification and all. Now:
* translations should be done on the ui side (see previous validation error
refactoring)
* consistent behaviour: each side (web/repo) is responsible to deal with its
request/session of language, no weird interaction between them on this topic
* drop on the way the 'session properties' api, used only for that matter.
-> much simpler/cleaner/saner api
The thing missing being a way for user to tell "My favorite language is xxx but I also
want cw to consider my http language header)
# copyright 2003-2012 LOGILAB S.A. (Paris, FRANCE), all rights reserved.
# contact http://www.logilab.fr/ -- mailto:contact@logilab.fr
#
# This file is part of CubicWeb.
#
# CubicWeb is free software: you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation, either version 2.1 of the License, or (at your option)
# any later version.
#
# CubicWeb is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
# FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
# details.
#
# You should have received a copy of the GNU Lesser General Public License along
# with CubicWeb. If not, see <http://www.gnu.org/licenses/>.
from warnings import warn
from logilab.common.deprecation import class_moved
warn('[3.15] moved to logilab.common.registry', DeprecationWarning, stacklevel=2)
from logilab.common.registry import *
VRegistry = class_moved(RegistryStore, old_name='VRegistry', message='[3.15] VRegistry moved to logilab.common.registry as RegistryStore')