[Bug 281470] math/py-numpy: Update to 2.1.1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470

--- Comment #13 from John Hein <jcfyecrayz@liamekaens.com> ---
(In reply to Michael Osipov from comment #11)
"... you need to have at least three to six months"

Whether that is an appropriate guideline depends on lots of factors that will
likely be different in different organizations (among FreeBSD ports tree
maintainers and the set of all downstream users).

One or two months gives some time, whereas comment 5 advocates zero.  I don't
know if six months would be acceptable to ports tree needs - it's hard to
juggle all the inter-dependencies of all the python ports, and things are
moving fast away from distutils, for instance.  There's not a perfect answer,
but I agree the FreeBSD ports tree updates should be balanced with
consideration of ports tree juggling and for downstream out-of-ports-tree
users.  And numpy1 would still be available after the cutover, so those
downstream ports tree users that did not muster the resources to migrate to
numpy2 "in time" would be able to switch to the numpy1 package until their
in-house uses could be updated.

As far as out-of-band (out-of-ports-tree) notice goes, I would recommend using
python@freebsd.org to communicate the plan that is settled on.  A wiki entry to
capture the plan, and guide users through the migration would be useful as
well.

I don't think a longer time window than a couple months would help much in many
cases. Take for example, the py2->py3 update - not a perfect comparison, but
lots of time passed to allow people to prepare for 2->3 update, and frequently
it prompted procrastination.  I still run into things (e.g., in-house scripts &
python libraries and other third party python-based dependencies not from the
FreeBSD ports tree) that need 2to3 treatment.

-- 
You are receiving this mail because:
You are the assignee for the bug.