|Summary:||math/py-pandas: Update to 0.25.2|
|Product:||Ports & Packages||Reporter:||John W. O'Brien <john>|
|Component:||Individual Port(s)||Assignee:||Wen Heping <wen>|
|Severity:||Affects Only Me||CC:||john, koobs, pi, python|
Description John W. O'Brien 2019-08-24 20:33:38 UTC
Created attachment 206865 [details] math/py-pandas: Update to 0.25.1 Changelog ========= * Update to 0.25.1 * Chase minimum versions of (soft) dependencies * Drop support for Python 2 QA == portlint: OK poudriere: OK -- testport on 11.3-RELEASE amd64 w/py35, py36 (default), py37
Comment 1 commit-hook 2019-09-09 01:28:37 UTC
A commit references this bug: Author: wen Date: Mon Sep 9 01:28:18 UTC 2019 New revision: 511603 URL: https://svnweb.freebsd.org/changeset/ports/511603 Log: - Update to 0.25.1 - Update DEPENDS PR: 240084 Submitted by: firstname.lastname@example.org(maintainer) Changes: head/math/py-pandas/Makefile head/math/py-pandas/distinfo
Comment 2 Wen Heping 2019-09-12 22:57:16 UTC
The update does not support python-2.7, so it will break some other ports. portmgr@ had reverted this commit. We should repocopy pandas to something like py-pandas-py27, but I would just wait, wait python2.7 deprecate from ports since python2.7 upstream will end of support soon :) wen
Comment 3 Kubilay Kocak 2019-09-13 04:40:38 UTC
(In reply to Wen Heping from comment #2) py-pandas-024 is fine as a name, and reflects the version branch the port uses, consistent with other uses within the tree. The py27 suffix would be confusing when coupled with the existing PKGNAME, ie: py27-pandas-py27
Comment 5 Kubilay Kocak 2020-05-22 03:44:12 UTC
(In reply to John W. O'Brien from comment #4) Upstream is now at 1.0.3 What does this mean for pandas024 pandas025 ports? Are they (all) still necessary regarding consumer dependents in terms of what versions they support?
Comment 6 John W. O'Brien 2020-05-22 14:10:18 UTC
(In reply to Kubilay Kocak from comment #5) I haven't studied the consumer dependents, nor pandas 1.0 for that matter, so I do not know whether any would have a problem chasing that update. Perhaps the best course of action would be to make a 25 port with a 3 month (e.g.) expiration, switching all consumers over to it and leaving it up to the respective maintainers to validate and adopt 1.0. Any consumer that still aims to support Python 2 would also still need access to a 24 port. It may no longer be worthwhile to implement the MUP-based dependency selection for py2/py3, because some consumers may need a 24/25 swing while others would prefer the 24/1.0 swing.
Comment 7 John W. O'Brien 2020-08-03 02:43:08 UTC
I am no longer the maintainer of this port.