Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide on a one true workflow for using polytracker #6565

Open
surovic opened this issue Nov 6, 2023 · 0 comments
Open

Decide on a one true workflow for using polytracker #6565

surovic opened this issue Nov 6, 2023 · 0 comments

Comments

@surovic
Copy link
Contributor

surovic commented Nov 6, 2023

We should probably still run tests with a couple Python versions though just in case.

Hmm, should we really? We essentially dictate the python version in the docker image build.

My reasoning here is that we have in the past allowed the use of different Python versions with Polytracker. If someone out there is using it with a prior Python version, it would be good to not arbitrarily take that support away from them. However, we only support Polytracker usage in the container, to the best of my knowledge, and as long as we're clear there's one true way to run Polytracker in the README, I don't see any reason to continue running builds or tests under any Pythons other than the Python version we prefer to build and run with.

Originally posted by @kaoudis in #6564 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant