On Thu, Sep 09, 2021 at 04:45:35AM +0000, Paul Wise wrote: >... > That seems like a bug in the test cases, they shouldn't be testing the > build time environment like that, since it could differ from the > runtime environment.
These are usually not the tests of dnspython. dnspython even has some support for using a different file instead of /etc/resolv.conf, the problem is that there are several other packages in the callstack before dnspython in these failing tests. Note that even if you would be mocking /etc/resolv.conf, you'd still have to add a nameserver IP address in the mocked /etc/resolv.conf At that point you might as well install the mocked resolv.conf as /etc/resolv.conf in build environments. > There are nss_wrapper/resolv_wrapper for mocking > away the build-time DNS resolving infrastructure. > > https://cwrap.org/nss_wrapper.html > https://cwrap.org/resolv_wrapper.html >... This is mocking the C library functionality, which is not used by dnspython. > bye, > pabs cu Adrian
