Open JavaScriptDude opened 3 years ago
Not a bad idea. What's the recommended way of doing that?
I have never done this before but here is my idea on how to make this an intuitive process.
#!/usr/bin/env python
from __future__ import annotations
from __future__ import print_function
3.7.10 Note: Python 3.7.10 has over 2.5 years of support left and I have come across some *nix distros that are still stuck at 3.7 (Eg Cygwin and Debian 10). I put a hard stop at 3.7.x for all my code bases for the time being because I have some production code running on Cygwin where using a higher release is very difficult to do.
Please don't do that (now). Our primary file server is running CentOS 7 - default python 2.7. Our "new" file servers and workstations are on RockyLinux 8: Defaulting to python 3.6.8 Current zfs supports starts with kernel 2.6.32 (!) So deprecate it, but be aware that CentOS 7 is EOL June 30, 2024. Nobody wants to update python in a production environment.
You are developing tools for zfs - and at least I select my file server OS by the length of its EOL Date.
I don't personally see a reason to kill py27 BUT the maintenance burden can be complicated (esp. w.r.t. types), and the oldest CentOS has had for a VERY long time Python 3.7 in the form ow EPEL.
So, what is the consensus here?
I'm neutral on this. Maybe hold off for now and do this once all major OS's are EOL'd off of 2.7.
As Python 2 has now been formally deprecated for over a year and is no longer receiving security updates, how about this project formally deprecate and no longer allow new release to run on Python 2. This will make maintaining the code much easier.
I just finished some querys of pypi data to see how many downloads there were of zfs-tools.
Here is the of zfs-tools downloads in last n months from PyPi:
Note: pypi does not store version information from all downloads so these numbers are a small subset of total downloads but should still be reflective of the big picture.
FYI - Data was retrieved from Google
https://console.cloud.google.com/bigquery
using the following SQL: