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

Decommission Python 3.6 build #1510

Open
poodlewars opened this issue Apr 19, 2024 · 1 comment
Open

Decommission Python 3.6 build #1510

poodlewars opened this issue Apr 19, 2024 · 1 comment

Comments

@poodlewars
Copy link
Collaborator

poodlewars commented Apr 19, 2024

No longer required.

Open question - what Pandas compat do we need? 3.6 build is the only one that tests Pandas 0.x compat. It would help the projects velocity to stop supporting Pandas 0.

This query in BigQuery shows that version 0 is extremely unpopular:

SELECT substring(file.version, 1, 1), COUNT(*) AS num_downloads
FROM `bigquery-public-data.pypi.file_downloads`
WHERE file.project = 'pandas'
  -- Only query the last 30 days of history
  AND DATE(timestamp)
    BETWEEN DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
    AND CURRENT_DATE()
group by substring(file.version, 1, 1)
order by 1
    ;

It hasn't been updated for 5 years.

Image

I think it's rational to remove support for it. Alternatively, we could test against it in the Python 3.8 build.

@poodlewars
Copy link
Collaborator Author

We need to be careful to continue to test backwards compat with Python 3.6 and Pandas 0. We should still have part of the CI that writes data in Python 3.6 with Pandas 0 and verify that later versions can work with it correctly. This is to make sure we don't break compat with already serialized data.

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