In order to keep implementation of class DSInstance organized, we implement all functionality as functions in separate modules. All functions accept DSInstance object as their first argument by rule. Even though its beneficial to define everythin as function in separate module, in runtime its nicer to have methods on DSInstance.
s beneficial to define everythin as function in separate module, in runtime it
ModuleProxy serves two purposes: - takes modules and all functions within and adds them to DSInstance as methods - creates separate namespaces for all modules within DSInstance
attachment 0001-Initial-commit-with-DSModuleProxy.patch
Added more unit tests and fixed args, kwargs of DSDecorator.
Thank you Rich ! Pushed to master.
{{{ [jrusnack@dhcp-31-42 ds-test]$ git push origin master Enter passphrase for key '/home/jrusnack/.ssh/id_rsa': Counting objects: 9, done. Delta compression using up to 4 threads. Compressing objects: 100% (7/7), done. Writing objects: 100% (8/8), 3.03 KiB, done. Total 8 (delta 0), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/ds-test.git 9bdbd64..8781017 master -> master }}}
Milestone lib389 1.0 deleted
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/895
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.