PYTHON-5382 - Add a test with min dependencies

[NoahStapp]

No description provided.

[NoahStapp]

Using uv sync --resolution=lowest-direct would try to install libmongocrypt and mockupdb. The approach taken here ensures we only install dnspython + pytest for the connect test suite.

[ShaneHarvey]

Where does this install the lowest version of dnspython we support? And don't we need to actually run a test suite that uses dnspython to confirm compatibility?

[NoahStapp]

Where does this install the lowest version of dnspython we support? And don't we need to actually run a test suite that uses dnspython to confirm compatibility?

Good catch, the --resolution=lowest-direct tag didn't get included in the commit. The original ticket Steve opened suggested the connect tests or srv, agreed that srv is a better suite to run here.

[NoahStapp]

dnspython didn't add resolver.resolve until 2.0.0: https://dnspython.readthedocs.io/en/latest/whatsnew.html#id12, but we explicitly test for it in test_import_dns_resolver. Added an or clause to the test to check for query instead for dnspython<2.0.0.

[ShaneHarvey]

Nice!

[ShaneHarvey]

Sorry I just noticed this was test_srv_polling but test_dns would probably be a better choice. Or both? And should we do both sync and async?

[NoahStapp]

Almost all of the test_dns tests require a sharded or replica cluster. We can add it here anyway, but it'll only add a handful of tests. And good catch, we should run sync and async tests here.

[ShaneHarvey]

Ah okay then, could you add a comment explaining why we use test_srv_polling only and not test_dns?

[ShaneHarvey]

Looks like test_dns's mocking is not compatible with dnspython 1.0. Perhaps it's not worth it to add in that case.

[NoahStapp]

And unfortunately there's no resolver.query method for the async resolver. I'll add a comment that the async test_dns is not compatible with dnspython 1.x, which is consistent with our docs for the async API.

[NoahStapp]

Adding a separate test for dnspython 2.0 for async support.

[NoahStapp]

Ended up having to use dnspython 2.1.0, as 2.0.0 does not include the lifetime kwarg we pass to our resolve calls, but only for the async API.

[ShaneHarvey]

Does that mean we have to update our docs and error message to say >=2.1 is required for async?

[NoahStapp]

Yes, I'll file a follow-up ticket for those changes.

[NoahStapp]

https://jira.mongodb.org/browse/PYTHON-5426