ports/lang/python31/files, branch 2016Q4

Remove lang/python31, it expired on 2014-06-01

2014-06-01T15:46:59Z

lang/python{31,32,33}: Fix stage/package as non-root

2014-04-22T12:14:26Z

Copy the second part of a change previously made to python27 [1], to python31, python32 and python33. This fixes staging and packaging of these ports by a non-root user by running ranlib on the archive prior to it being installed read-only. While I'm here: - python27: Add breadcrumbs and references to the patch header - python34: Update breadcrumbs and references to the patch header [1] https://svnweb.freebsd.org/ports?view=revision&revision=350207 Submitted by: antoine Reviewed by: kwm, sbz

lang/python{31,32,33}: Add clang 3.4 fix from python27

2014-04-20T01:35:39Z

Copy change committed to python27 [1] to python31, python32 and python33 to fix builds of some extensions with Clang 3.4. Also add breadcrumbs to the patch header in lang/python27 referencing the upstream issue. [2] The Python 3.4 port (lang/python34) already carries the patch. [1] https://svnweb.freebsd.org/ports?view=revision&revision=346428 [2] http://bugs.python.org/issue20767

- Fix build with readline 6.3 from ports

2014-03-01T15:53:29Z

the patch was backported from upstream (issue #20374) - Add missing USES=readline Obtained from: python

lang/python*: Backport security fix for CVE-2014-1912

2014-03-01T10:52:55Z

A vulnerability was reported [1] in Python's socket module, due to a boundary error within the sock_recvfrom_into() function, which could be exploited to cause a buffer overflow. This could be used to crash a Python application that uses the socket.recvfrom_info() function or, possibly, execute arbitrary code with the permissions of the user running vulnerable Python code. This vulnerable function, socket.recvfrom_into(), was introduced in Python 2.5. Earlier versions are not affected by this flaw. This is fixed in upstream branches for version 2.7, 3.1, 3.2 and 3.3. [1] http://bugs.python.org/issue20246 MFH: 2014Q1 Security: 8e5e6d42-a0fa-11e3-b09a-080027f2d077

lang/python31: Backport fox for Python issue #8168

2014-02-21T13:42:08Z

- Backport Python issue #8168 [1]: python3 py_compile does not ignore UTF-8 BOM characters This causes installation (during bytecode compilation) errors for Python ports with sources that contain BOM characters [2] The issue was fixed [3] in the default branch at the time (3.2) but was not backported to 3.1. Since Python 3.1 is now in security-fix-only mode (no new features or bug fixes), backporting is required. [1] http://bugs.python.org/issue8168 [2] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/186034 [3] http://hg.python.org/cpython/rev/e15a8a476494/ PR: ports/186034 Reported by: Mark Andrews

All Python ports: Address abort() for ctypes import on FreeBSD/ARM

2013-12-08T06:22:07Z

The current FreeBSD/ARM __clear_cache() implementation does nothing #if __i386__ || __x86_64__ #else abort(); cognet@ advises this is an issue for anything !Apple that is using the libcompiler_rt provided by Clang on ARM, and requires upstreaming. This is the root cause of abort() on import for the ctypes module in Python, as they bundle libffi. [1] This change patches the bundled libffi library in all Python ports, even though it is a NOOP for the ports that use devel/libffi. These ports, currently python31, will get the fix via ports/184517 A huge shout out to cognet@ who helped diagnose the issue and created the patch to address it. Thank you! PR: ports/149167 [1] PR: ports/184517 Submitted by: cognet [3] Reviewed by: cognet, eadler, milki, ak

Fix OSS Audio and enable FreeBSD 11 support in Python 3.2 and 3.1

2013-12-01T12:25:37Z

- Add the appropriate Python platform (plat-*) files for FreeBSD 11 - Update pkg-plist Backport a upstream change [1] removing OS major version from the check to enable the OSS Audio module in setup.py: Issue #12326: don't test the major version of sys.platform Use startswith, instead of ==, when testing sys.platform to support new platforms like Linux 3 or OpenBSD 5. [2] [1] http://hg.python.org/cpython/rev/50f1922bc1d5 [2] http://bugs.python.org/issue12326

lang/python31: Backport upstream kevent fix and use libffi from ports

2013-12-01T09:34:20Z

Backport a change fixing use of kevent flags that was merged to Python default, 3.3 and 2.7 branches, but not 3.2 and 3.1 that were in security-only mode at the time of commit. [1] - Add patch: patch-Modules__selectmodule.c Based on patch by: David Naylor Unconditionally use libffi from ports because the Python 3.1 branch was closed for maintenance when the import of libffi 3.0.13 took place. This fixes _ctypes module build failure on i386. [2] - Add global CONFIGURE_ARGS and LIB_DEPENDS References: [1] Issue #11973: Fix a problem in kevent. The flags and fflags fields are now properly handled as unsigned. [#11973] http://bugs.python.org/issue11973 http://hg.python.org/cpython/rev/8345fb616cbd [2] Fixes Issue #17192: Update the ctypes module's libffi to v3.0.13. This specifically addresses a stack misalignment issue on x86 and issues on some more recent platforms. [#17192] http://bugs.python.org/issue17192 http://hg.python.org/cpython/rev/a94b3b4599f1 http://hg.python.org/cpython/rev/688bc0b44d96 While I'm here: - Add LICENSE (PSFL) - Clean up & whitespace alignment PR: ports/156759 [1] Reviewed by: mva

- Update:

2012-04-11T12:52:17Z

* python26 -> 2.6.8 * python27 -> 2.7.3 * python31 -> 3.1.5 * python32 -> 3.2.1 Security: http://www.vuxml.org/freebsd/b4f8be9e-56b2-11e1-9fb7-003067b2972c.html CVE-2012-0845 CVE-2012-0876 CVE-2012-1150 CVE-2012-0845 CVE-2011-3389