Add support for Python 3.11

[iknox-fa]

resolves #6147

Description

Adds support for Python 3.11 :sonic:

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[jtcohen6]

More tests passing locally. mypy is unhappy with the hack I've taken here, where I "call" our Policy objects as a way of initializing all their dataclass properties (now that they're default_factory instead of default). I'm sure there's a better way to do this!

[jtcohen6]

Per failing unit tests, looks like this needs fixing for py311:

dbt-core/tests/unit/test_version.py

Lines 638 to 648 in b5d303f

	def mock_import(*args, **kwargs):
	mock_module = mocker.Mock()
	mock_module.version = "1.0.0"
	import_path = args[0]
	for plugin in plugins:
	if plugin in import_path:
	return mock_module
	raise ImportError

[MichelleArk]

Per failing unit tests, looks like this needs fixing for py311:

Took a look into this - I believe the root cause here is that mock.patch now uses importlib.import_module indirectly python 3.11 and thus uses the mocked object (in this case, mock_import) instead of the real implementation in subsequent mock.patch calls, raising an ImportError.

The change in unittest is here. A related-looking issue was opened in cpython, but closed as not planned. One (not great, fragile) way to work around this is to swap the order of execution in test_versions.py, such that the importlib.import_module patch is the last to be mocked.

[jtcohen6]

(not great, fragile)

@MichelleArk Given that this is just a method in our unit tests (quite old, probably warranting a rewrite), I don't hate the idea of a quick & expedient fix, whose fragility we can document for our future selves

[MichelleArk]

Just one comment - otherwise LGTM! 🐍 🏃💨

[jtcohen6]

I think I managed to fix the failure in test_logging.py for py311.

Less sure why tests/adapter/grants suddenly started failing, claiming that the env vars for test users weren't set:

Env var required but not provided: 'DBT_TEST_USER_X'

Update: This is due to a breaking change in tox==4.0.0, see #6405

[jtcohen6]

@peterallenwebb This seems to have been an unintentional change in #6291, where the file text log looked like:

�[0m18:00:14.981418 [EventLevel.INFO] [MainThread]: Running with dbt=1.4.0-a1
�[0m18:00:14.982553 [EventLevel.DEBUG] [MainThread]: running dbt with arguments {'write_json': True, 'use_colors': True, 'printer_width': 80, 'version_check': True, 'partial_parse': True, 'static_parser': True, 'profiles_dir': '/Users/jerco/.dbt', 'send_anonymous_usage_stats': True, 'quiet': False, 'no_print': False, 'which': 'run', 'rpc_method': 'run', 'indirect_selection': 'eager'}

Instead of:

�[0m18:10:46.308814 [info ] [MainThread]: Running with dbt=1.4.0-a1
�[0m18:10:46.309953 [debug] [MainThread]: running dbt with arguments {'write_json': True, 'use_colors': True, 'printer_width': 80, 'version_check': True, 'partial_parse': True, 'static_parser': True, 'profiles_dir': '/Users/jerco/.dbt', 'send_anonymous_usage_stats': True, 'quiet': False, 'no_print': False, 'which': 'run', 'rpc_method': 'run', 'indirect_selection': 'eager'}

Caught because this logging test checks log lines for the presence of the string ["debug"] exactly.

Update: It looks like this may have been a specific behavior change in Python 3.11, related to how enums are stringified / formatted (python/cpython#94763)

[jtcohen6]

I noticed that e.log_level() generally returns an EventLevel enum, but sometimes it just returns a str for DynamicLevel events (added in #6174). This was causing tests to hang (because exceptions in our logging code don't bubble up). I've handled this with a kinda janky ternary for now: 9c0af3f

[jtcohen6]

@peterallenwebb says this is fine for now, we'll open a tech debt issue for the str/enum inconsistency :)