Date: Tue, 26 Sep 2023 19:01:31 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 274099] lang/python27 fails to compile on 14.0-BETA2 Message-ID: <bug-274099-21822-GOstgZVe5q@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-274099-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-274099-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=3D274099 --- Comment #19 from John Hein <jcfyecrayz@liamekaens.com> --- (In reply to Charlie Li from comment #18) Ok. Your (python team) call, of course. The patch is fairly trivial and worthwhile, so it could help people. I know there are a lot of python2 users still out there (despite the upstre= am status). I'm not saying that's good or bad, just that "it is". I confess,= I still use it for scripts that haven't been ported or have not been gotten m= uch testing under py3 yet. I appreciate that the ports team allowed py27 to st= ill exist (thankfully, it hasn't been a huge burden, I think). That friendly treatment been very useful to end users in my circle. It can be frustratin= g to get hit with aggressive deprecation action when there are old (and reliable) systems in production. I did test that openssl32 works fine with the python27 port. Specifically I hard coded the proper ssl version in setup.py, built python27 based on that= and did some basic hashlib testing successfully - so that's good news. Anyway... hopefully the patch will help some people who can apply it locall= y. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-274099-21822-GOstgZVe5q>