[CT-653] [Feature] Allow running unit/integration tests locally with any supported Python version #5257
Closed
1 task done
Labels
enhancement
New feature or request
good_first_issue
Straightforward + self-contained changes, good for new contributors!
Is this your first time opening an issue?
Describe the Feature
This is more of a rough edge for a non-professional dbt-core developer: the
Makefile
hard-codespy38
as the preferred python version in tox for running unit tests and integration tests; we use Python 3.9 at my day job, so when I need to do work on dbt-core I need to remember to swap out the version in the Makefile topy39
before I run dbt tests and then switch it back before I send a PR upstream.Describe alternatives you've considered
I would love it if the Makefile was either a) configured to work with the Python version that I had installed locally as long as it was supported (i.e., if the default in the Makefile was
py
andpy-integration
instead ofpy38
andpy38-integration
), or, if that presents a problem for e.g. CI or some such thing, if it was easy (like via an environment variable that was documented in theCONTRIBUTING.md
guide) for me to override the setting in theMakefile
on my local machine.Who will this benefit?
Developers who want to create PRs for dbt-core who do not work at dbt Labs.
Are you interested in contributing this feature?
Happy to!
Anything else?
Issue originally discussed in a Slack thread in dbt-core-development: https://getdbt.slack.com/archives/C50NEBJGG/p1652466095907019
The text was updated successfully, but these errors were encountered: