chore: bump python version to 3.11 in Dockerfile

[tooptoop4]

SUMMARY

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[rusackas]

Pinging @villebro and @EugeneTorap as I believe you've wrangled with this in the past, and know the perils and pitfalls here better than most :)

[EugeneTorap]

Hi @tooptoop4!
We use the minimum supported python version in the Dockerfile. It's 3.8 version.
But we can push a docker image with python 3.11 - look at #22770 PR how to do it!
@villebro @dpgaspar can we rid 3.8 & 3.9 PY versions of in superset 3.0 and use only 3.10 & 3.11 PY versions? In superset 4.0 we'll rid 3.10 PY version of and will use only 3.11 & 3.12 PY versions. What do you think?

[villebro]

@EugeneTorap I agree, we should bump to 3.10 as the official version. Would you be up for making the changes?

[EugeneTorap]

@villebro Yes, I want to do it!

[mdeshmu]

I have raised the PR to add support for 3.11

[EugeneTorap]

@mdeshmu We use the minimum supported version of Python in Dockerfile! It's Py3.9 because a lot of drivers don't have support Py3.10 & Py3.11 (for example: PyHive don't have support the new versions of python)

[mdeshmu]

I am not changing the default image version which supports 3.9. I just added the ability to create additional images with 3.11 so that we can use it with Superset's code base.
Talking of database drivers, Many of the drivers we use, do support Py 3.11. For e.g. pyathena, redshift-connector, pyscopg2 and many more.

[EugeneTorap]

@mdeshmu, I agree with you but @sebastianliebscher and me are working on updating the minimum PY version of the superset from 3.9 to 3.10 and use only 3.10 & 3.11 here.

[mdeshmu]

I didn't clearly understand your last comment.
I saw @sebastianliebscher's PR in which he has made python 3.9 as default and added support for 3.10 additional images.
I have just extended that work and added support for 3.11 additional images in this PR.

[EugeneTorap]

@mdeshmu Yes, we will soon have a PR for Bump to Python3.10 where we only use 3.10 and 3.11 PY for docker images.

[mdeshmu]

Would that be with Superset 3.0 release or earlier ?

[EugeneTorap]

Yeap, we plan to use only PY 3.10 & 3.11 in Superset 3.0

[EugeneTorap]

If you have a slack account in apache/superset you can join #server-refactoring channel and help us to fix PyHive for PY 3.10

[rusackas]

@EugeneTorap @villebro @tooptoop4 is this PR still relevant? It looks like we're still on 3.9.

[mistercrunch]

Closing this in favor or #24112