Date: Mon, 01 Feb 2021 21:21:23 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 252117] devel/py-llfuse: Update to 1.3.8 Message-ID: <bug-252117-21822-4jeZBZs7OW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252117-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-252117-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252117 --- Comment #10 from Yuri Victorovich <yuri@freebsd.org> --- (In reply to John Hein from comment #9) It's a small nuance. The port can get limited to python:3.6+ for 2 reasons: 1. When it doesn't build with python-2.7 2. When some dependency is broken or incompatible with python-2.7 In this case 2. is the true. If/once this dependency is fixed someone would just change python:3.6+ -> python in devel/py-llfuse. And this port would be left broken for python-2.7. Yes, it's best to look a= nd retest when doing this, but the reality is different and often people don't retest. This is my rationale for this line. On the other side, what is the downside? There's really none, it's just a l= ine. It doesn't force python-2.7 or change the behavior in any way. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252117-21822-4jeZBZs7OW>