Date: Sat, 7 Dec 2019 10:12:37 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Dima Pasechnik <dimpase+freebsd@gmail.com> Cc: FreeBSD Ports <freebsd-ports@freebsd.org>, Adam Weinberger <adamw@adamw.org> Subject: Re: python36 is still broken. Message-ID: <20191207181237.GA3896@troutmask.apl.washington.edu> In-Reply-To: <CAAWYfq16ik9ZnRWFZjZPQEHsi9q=n==OWie5=rPN3z1LNFsm6w@mail.gmail.com> References: <20191206184050.GA44417@troutmask.apl.washington.edu> <CAP7rwcj00Z81VBJ47dFfn1RUJFCb1rBAW77pP7Wj=BxRdZFp6g@mail.gmail.com> <20191206230329.GC949@troutmask.apl.washington.edu> <CAAWYfq16ik9ZnRWFZjZPQEHsi9q=n==OWie5=rPN3z1LNFsm6w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 06, 2019 at 11:30:29PM +0000, Dima Pasechnik wrote: > The patch in question is in Python 3.7, cf. > https://github.com/python/cpython/pull/12046 > how about switching to this version? > Is 3.7 the default version of python used by ports? How does switching fix ports that require 2.7? I'll simply be direct. It is a 2-line patch that renames a static function in a single file. Why is so difficult for python@ and/or ports@ to include the patch for the various python ports. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191207181237.GA3896>