Date: Tue, 17 Jun 2014 13:22:16 +0200 From: Marcus von Appen <mva@freebsd.org> To: freebsd-python@freebsd.org Subject: Re: Python 2.7.7 Message-ID: <20140617132216.Horde.Lce6wqtFBWF13HgfAJ18Sg1@webmail.df.eu> In-Reply-To: <CAKBkRUy6hr2bNVudF3%2BzzvDiMiWStPLD6c1R1w1JH_%2BOKcJxJA@mail.gmail.com> References: <CA%2BQLa9AJD6b=SF7enB-YQFDw=p=ChLS6eExkH9WEsoz2rvJ3Pg@mail.gmail.com> <CAKBkRUy6hr2bNVudF3%2BzzvDiMiWStPLD6c1R1w1JH_%2BOKcJxJA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Li-Wen Hsu <lwhsu@freebsd.org>: > On Wed, Jun 11, 2014 at 1:54 AM, Robert Simmons <rsimmons0@gmail.com> wrote: >> Is there an ETA for updating the python27 port to 2.7.7? > > I just made a patch for updating python27: > > https://people.freebsd.org/~lwhsu/patch/python-2.7.7.diff lang/python27/files/patch-Lib__distutils__unixccompiler.py should be kept. http://bugs.python.org/issue20767 has not been closed yet and the 2.7.7 source code does not incorporate the change nor does the NEWS file indicate anything related to the issue. I'm also unsure about the fcntl.ioctl() patch change. The 2.7.6 patch used an unsigned long on purpose, since we are not limited to 32 bit. The 2.7.7 patch however seems to revert this behaviour, limiting ioctl() to 32 bit, which will most likely have an impact on ports using ioctl(). I can't find a related python issue - did we ever report our change upstream? Cheers Marcus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140617132216.Horde.Lce6wqtFBWF13HgfAJ18Sg1>