[GH-ISSUE #13] Remove support for python 2.7 #5

New issue

Closed

opened 2026-02-27 15:45:56 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 15:45:56 +03:00

Owner

Originally created by @CompileNix on GitHub (Mar 21, 2020).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/13

Originally assigned to: @jhollowe on GitHub.

Python 2.7 is officially end-of-life since Jan 1, 2020.

So, i would argue that we should remove support for python 2.7 in the near feature.

Originally created by @CompileNix on GitHub (Mar 21, 2020). Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/13 Originally assigned to: @jhollowe on GitHub. Python 2.7 is officially [end-of-life since Jan 1, 2020](https://www.python.org/doc/sunset-python-2/). So, i would argue that we should remove support for python 2.7 in the near feature.

kerem

2026-02-27 15:45:56 +03:00

closed this issue
added the
type:meta
label

kerem commented

2026-02-27 15:45:56 +03:00

Author

Owner

@jhollowe commented on GitHub (Apr 21, 2020):

While I agree Python 2 should disappear, that takes effort from the entire community. While I would encourage all development in the future to prioritize 3.x, removing existing Python 2 support doesn't make sense. There is still likely 2.7 code that is using this library which we should not force to update until there is a reason to do so.

If there is a feature we would like to implement in the future that requires 3.x I would push to include it and end support for 2.x. However, code that does not require 3 should continue using existing cross-version code.

If you have a good reason to end 2.7 support, I would love to hear it and consider it, but as I see it, we don't need to do so at the current time.

TL;DR I would like to keep 2.x until there is a code-base reason to remove support.

@jhollowe commented on GitHub (Apr 21, 2020): While I agree Python 2 should disappear, that takes effort from the entire community. While I would encourage all development in the future to prioritize 3.x, removing existing Python 2 support doesn't make sense. There is still likely 2.7 code that is using this library which we should not force to update until there is a reason to do so. If there is a feature we would like to implement in the future that requires 3.x I would push to include it and end support for 2.x. However, code that does not *require* 3 should continue using existing cross-version code. If you have a good reason to end 2.7 support, I would love to hear it and consider it, but as I see it, we don't *need* to do so at the current time. TL;DR I would like to keep 2.x until there is a code-base reason to remove support.

kerem commented

2026-02-27 15:45:56 +03:00

Author

Owner

@jhollowe commented on GitHub (May 15, 2020):

I'm going to close this, but anyone one in the future feel free to comment

@jhollowe commented on GitHub (May 15, 2020): I'm going to close this, but anyone one in the future feel free to comment

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/proxmoxer#5

No description provided.

Rows
Columns