Hi, I've now closed and finished #48820 and #48853. There is still a long way to go but we've hit some major goals here. I just don't want these tickets to keep growing! We now have a new way to manage objects in lib389, and we are starting to use them, and work out the kinks. The best for this to happen is for me / other interested to re-write the lib389 tests to consume these. We also have a huge about of progress on python3. The scorecard is at the bottom of this email. Going forwards, I'm going to close these, as I've implemented the new api. I'm going to start opening tickets related to re-work of the existing apis to consume this, including improvement to the tests in lib389. Once those are all complete, and we have an idea of what it should look like / have shaken out the issues, I would start working on deprecating the old apis, and re-working our current set of dirsrvtests. What do we think of this as a plan? It's likely a good 6 months before this is complete, but no time like the present to get started. By the end we should be completely python 3 ready, and have a much easier interface to prepare us for rest389 / other tools. Would love to hear comments on this, -- score card: python 2: platform linux2 -- Python 2.7.11, pytest-2.9.1, py-1.4.31, pluggy-0.3.1 rootdir: /home/wibrown/development/389ds/lib389, inifile: collected 66 items lib389/lib389/tests/aci_test.py .. lib389/lib389/tests/agreement_test.py .......F lib389/lib389/tests/backend_test.py ..... lib389/lib389/tests/dereference_test.py . lib389/lib389/tests/dirsrv_log_test.py ... lib389/lib389/tests/dirsrv_test.py ..... lib389/lib389/tests/effective_rights_test.py . lib389/lib389/tests/entry_test.py ...... lib389/lib389/tests/krb5_create_test.py . lib389/lib389/tests/ldclt_test.py . lib389/lib389/tests/mappingTree_test.py ..... lib389/lib389/tests/nss_ssl_test.py . lib389/lib389/tests/replica_test.py ....... lib389/lib389/tests/schema_test.py . lib389/lib389/tests/suffix_test.py ... lib389/lib389/tests/test_module_proxy.py ........ lib389/lib389/tests/utils_test.py ........ python 3: platform linux -- Python 3.5.1, pytest-2.9.1, py-1.4.31, pluggy-0.3.1 rootdir: /home/wibrown/development/389ds/lib389, inifile: collected 66 items lib389/lib389/tests/aci_test.py .. lib389/lib389/tests/agreement_test.py EEEEEEEE lib389/lib389/tests/backend_test.py .FFFF lib389/lib389/tests/dereference_test.py F lib389/lib389/tests/dirsrv_log_test.py ... lib389/lib389/tests/dirsrv_test.py EEEEE lib389/lib389/tests/effective_rights_test.py F lib389/lib389/tests/entry_test.py .....F lib389/lib389/tests/krb5_create_test.py E lib389/lib389/tests/ldclt_test.py F lib389/lib389/tests/mappingTree_test.py .FFF. lib389/lib389/tests/nss_ssl_test.py F lib389/lib389/tests/replica_test.py FFFFFF. lib389/lib389/tests/schema_test.py . lib389/lib389/tests/suffix_test.py FFF lib389/lib389/tests/test_module_proxy.py ........ lib389/lib389/tests/utils_test.py ........ -- Sincerely, William Brown Software Engineer Red Hat, Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
-- 389-devel mailing list 389-devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/389-devel@xxxxxxxxxxxxxxxxxxxxxxx
