Tue, 23 Apr 2013 17:58:20 +0200 [test/ldap] have RQL2LDAPFilterTC use its own database
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 17:58:20 +0200] rev 8903
[test/ldap] have RQL2LDAPFilterTC use its own database I do not know what RQL2LDAPFilterTC is about and why it does this strange reuse of LDAPUserSourceTC pre_setup_database but it is certainly a good idea to have it use a dedicated database-cache.
Tue, 23 Apr 2013 16:25:56 +0200 [ldap] quieter tests
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 16:25:56 +0200] rev 8902
[ldap] quieter tests Capture slapadd and slapd output if everything goes well.
Wed, 10 Apr 2013 17:50:11 +0200 [test/ldap source] better source naming, some cleanups (prepares #2528116)
Jérôme Roy [Wed, 10 Apr 2013 17:50:11 +0200] rev 8901
[test/ldap source] better source naming, some cleanups (prepares #2528116) ldap uri becomes "ldap" in all cases prepare separation of CONFIGs by source type
Tue, 23 Apr 2013 15:33:50 +0200 use cw_etype instead of __regid__
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 15:33:50 +0200] rev 8900
use cw_etype instead of __regid__ We have a clean public API now.
Tue, 23 Apr 2013 15:16:36 +0200 [entity] add an official ``cw_etype`` property for entity
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 15:16:36 +0200] rev 8899
[entity] add an official ``cw_etype`` property for entity This property holds the CWEtype id of the entity. This information was previously available through __regid__ but this is an ugly public API. So we have a new clean public API. The ``dc_type()`` method could not be used as it is translated. (closes #2793792)
Tue, 23 Apr 2013 12:38:27 +0200 [notification] use new style operation for notification
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 12:38:27 +0200] rev 8898
[notification] use new style operation for notification This results in far less operations created. Operation creation is expensive. We keep some compatibility with the previous API because some cubes have been reported to use it.
Mon, 22 Apr 2013 17:16:02 +0200 [cleanup] drop code deprecated since 3.6
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 22 Apr 2013 17:16:02 +0200] rev 8897
[cleanup] drop code deprecated since 3.6 The 3.6 API have been dropped some time ago. Those three lines survived the purge. One of them is even deprecated since 3.5.
Mon, 22 Apr 2013 15:25:04 +0200 [notification] fix documentation
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 22 Apr 2013 15:25:04 +0200] rev 8896
[notification] fix documentation The doc say precommit, the code says postcommit. The code is right. We also clarify the documentation of another related operation looking suspiciously wrong but actually correct.
Tue, 23 Apr 2013 12:01:14 +0200 [ldapuser] Deprecated the source
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 23 Apr 2013 12:01:14 +0200] rev 8895
[ldapuser] Deprecated the source We have ldapfeed for some time. maintaining both is cumbersome. This old style source will be dropped in 3.18. closes #2567712
Fri, 19 Apr 2013 15:44:42 +0200 [rql2sql] Remove an XXX by explaining why Int non-substitution is desired
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Apr 2013 15:44:42 +0200] rev 8894
[rql2sql] Remove an XXX by explaining why Int non-substitution is desired (in the current state of the API)
Fri, 19 Apr 2013 15:41:56 +0200 [rql2sql] Boolean values should be substitued like others. Closes #2829481
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Apr 2013 15:41:56 +0200] rev 8893
[rql2sql] Boolean values should be substitued like others. Closes #2829481 Furthermore lgdb 1.10 deprecate boolean_value method and this simplify testing.
Mon, 22 Apr 2013 14:54:22 +0200 [toward-py3k] rewrite __cmp__ (closes #2715115)
Nicolas Chauvat <nicolas.chauvat@logilab.fr> [Mon, 22 Apr 2013 14:54:22 +0200] rev 8892
[toward-py3k] rewrite __cmp__ (closes #2715115) In Python 3k `__cmp__` special method is no longer supported. So we split it in `__lt__` and `__eq__`. details on Python3k behavior here: http://docs.python.org/3.0/whatsnew/3.0.html#ordering-comparisons
(0) -3000 -1000 -300 -100 -12 +12 +100 +300 +1000 +3000 tip