diff options
| author | Philipp Hagemeister <phihag@phihag.de> | 2018-06-10 12:17:46 +0200 |
|---|---|---|
| committer | Philipp Hagemeister <phihag@phihag.de> | 2018-06-10 12:17:46 +0200 |
| commit | 242b347ba0e155b45909ecbca73da53f67be4030 (patch) | |
| tree | 98a4b390de6adc730ebcb765aad1b7d59263e607 | |
| parent | 3561913eee7b8457cf4a8115cfb4129f0bd528f6 (diff) | |
| download | platform_external_python_ipaddress-242b347ba0e155b45909ecbca73da53f67be4030.tar.gz platform_external_python_ipaddress-242b347ba0e155b45909ecbca73da53f67be4030.tar.bz2 platform_external_python_ipaddress-242b347ba0e155b45909ecbca73da53f67be4030.zip | |
OTHER_BACKPORTS: Update text
| -rw-r--r-- | OTHER_BACKPORTS.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/OTHER_BACKPORTS.md b/OTHER_BACKPORTS.md index 04c6371..5e79111 100644 --- a/OTHER_BACKPORTS.md +++ b/OTHER_BACKPORTS.md @@ -19,7 +19,7 @@ In addition, judging by http://pypi-ranking.info/search/ipaddress/ , this backpo sk-/backport_ipaddress is a fork of kwi/py2-ipaddress. As you can see from the above dates, the project has basically never been updated after being released. So I'm just going to focus on my ipaddress vs py2-ipaddress. Mine has nearly 40x the download count. -As you can also see from the above stats, py2-ipaddress has not been updated for over a year. Sure, it's a backport and thus does not necessitate frequent updating, but for instance cPython has fixed a couple of bugs just recently, and they are certainly still present in py2-ipaddress. In contrast, I can and do regularly sync. Upstream cPython code is in the upstream branch and just gets merged, so you can sync if you need the bleeding-edge ipaddress code (but a pull request or issue would be fine too if that's what you need). +As you can also see from the above stats, py2-ipaddress has not been updated for over two years. Sure, it's a backport and thus does not necessitate frequent updating, but for instance cPython has fixed a couple of bugs just recently, and they are certainly still present in py2-ipaddress. In contrast, I can and do regularly sync. Upstream cPython code is in the upstream branch and just gets merged, so you can sync if you need the bleeding-edge ipaddress code (but a pull request or issue would be fine too if that's what you need). But I don't think it's even necessary to argument from metadata, when the technical facts speak for themselves: |