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

[FEATURE] Requesting brickflow support for python versions 3.11 and 3.12 #84

Open
1 of 4 tasks
raajaaDheeRaajaa opened this issue Jan 19, 2024 · 2 comments
Open
1 of 4 tasks
Labels
enhancement New feature or request

Comments

@raajaaDheeRaajaa
Copy link

Is your feature request related to a problem? Please describe.
Currently, the compatible versions of python for brickflow are pinned to 3.8, 3.9 & 3.10

python = ">=3.8,<3.11" # pyspark <3.5 does not play happy with python 3.11

Requesting to add support for python versions 3.11 & 3.12, for users using pyspark version >=3.5

Cloud Information

  • AWS
  • Azure
  • GCP
  • Other

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
Updating the acceptable python version from >=3.8,<3.11 to >=3.8,<=3.12 here:

python = ">=3.8,<3.11" # pyspark <3.5 does not play happy with python 3.11

Additional context
This change will allow users running newer version of python with new features and bug fixes, able to use brickflow.

@raajaaDheeRaajaa raajaaDheeRaajaa added the enhancement New feature or request label Jan 19, 2024
@t1ffanyt
Copy link

Hello, I can take up this issue and test brickflow with the updated python versions.

@stikkireddy
Copy link
Collaborator

Hey team, intentially we are supporting 3.8 - 3.10 as those are the system versions supported by databricks runtimes.
14.3 LTS beta is provided with Python: 3.10.12
https://docs.databricks.com/en/release-notes/runtime/14.3lts.html#system-environment

The risk of supporting higher versions is it may encourage users to use newer 3.11, 3.12 and 3.13 features which may not work on 3.10. The user will not run into this without, actually running their workflow.

I am not opposed to this change, as the library should work in higher versions (since new versions of python contain all the previous features) but I do not know of a good way to indicate to the user to not use 3.11+ features. Let me know if you have any ideas around that.

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

No branches or pull requests

3 participants