Fri, 07 Dec 2012 17:23:04 +0100 remove vreg argument to CWPublisher
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 07 Dec 2012 17:23:04 +0100] rev 9030
remove vreg argument to CWPublisher The passing a vreg to CWPublisher was used by test to allow reused of an existing vreg. We dropped this feature two commit ago and can safely removes it. Removing this argument allows later cleanup and improvement on the CWPublisher and Repository front. closes #2944813
Fri, 07 Dec 2012 16:10:38 +0100 [devtools] vreg becomes a class ppty
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 07 Dec 2012 16:10:38 +0100] rev 9029
[devtools] vreg becomes a class ppty After multiple devtools refactoring, the vreg used for test is now *always* got from the repository. Making this explicit is a step toward simplification of the vreg handling during various initialisation phases. Related to #2944813
Fri, 23 Nov 2012 16:33:00 +0100 [devtools] drop unused `reset_schema` and `reset_vreg` class attribute
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 23 Nov 2012 16:33:00 +0100] rev 9028
[devtools] drop unused `reset_schema` and `reset_vreg` class attribute They have no effect and no user... Related to #2944813
Mon, 27 May 2013 17:50:55 +0200 [connection] move security control logic on Connection
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 27 May 2013 17:50:55 +0200] rev 9027
[connection] move security control logic on Connection The _security_enabled context manager now operate on connection. We have to keep a specific entry point in Session to ensure Connection object are properly cleaned up when using session to "manage" Connection live cycle. Related to #2503918
Fri, 14 Jun 2013 12:11:42 +0200 [connection] move hook control logic on Connection
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 14 Jun 2013 12:11:42 +0200] rev 9026
[connection] move hook control logic on Connection The _hook_control context manager now operate on connection. We have to keep a specific entry point in Session to ensure Connection object are properly cleaned up when using session to "manage" Connection live cycle. Related to #2503918
Fri, 14 Jun 2013 12:10:45 +0200 [session] update _hook_control docstring
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 14 Jun 2013 12:10:45 +0200] rev 9025
[session] update _hook_control docstring
Mon, 27 May 2013 16:43:02 +0200 [connection] reinstall cnx.data as cnx.transaction_data
pierre-yves [Mon, 27 May 2013 16:43:02 +0200] rev 9024
[connection] reinstall cnx.data as cnx.transaction_data Too much code expects self._cw.data to be session data. backout 9b2f68916474 Related to #2503918 Related to #2912807
Mon, 27 May 2013 16:42:39 +0200 [connection] give access to is_internal_session boolean
pierre-yves [Mon, 27 May 2013 16:42:39 +0200] rev 9023
[connection] give access to is_internal_session boolean Needed if we are to use this object like we currently do with session. Related to #2503918
Fri, 14 Jun 2013 13:39:49 +0200 [req] drop from_controller on non WebRequest object (Closes #2901079)
pierre-yves [Fri, 14 Jun 2013 13:39:49 +0200] rev 9022
[req] drop from_controller on non WebRequest object (Closes #2901079) The `controller` concept is purely a web things. It does not belong to generic `req` object. The `build_url` code is slightly changed to handle that. This probably requires extended cleanup later. This is a barely used and very internal API. No deprecation period
Tue, 14 May 2013 00:36:43 +0200 [connection] add logging method on connection
pierre-yves [Tue, 14 May 2013 00:36:43 +0200] rev 9021
[connection] add logging method on connection If we are to use this object like we currently do with session, we need to have the logging method as a lot of code use them.
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip