Also, the ldapcherry dependency are already packaged by CentOS (with Epel) and Debian/Ubuntu, I should probably mention it and document it, it will be less fragile than pip.
Did you want to have the packages in the requirements*.yml files installed with the OS's package management rather than having pip do the install when running setup.py?
Coverage remained the same at 80.757% when pulling b9743ef9d04ee7147b285bfef1b7570340377c9a on smacz42:andrewcz-ldapcherry-issue36 into 856157af799dc54ab66ef0e58d0c68fdcfb9b5cc on kakwa:master.
Addresses #36 and #35
However, when you said in https://github.com/kakwa/ldapcherry/issues/36#issuecomment-489044821:
Did you want to have the packages in the
requirements*.yml
files installed with the OS's package management rather than havingpip
do the install when runningsetup.py
?