ports/lang/python30, branch 2025Q3

- Get rid python-2.3 and python-3.0 (no longer under developement)

2009-12-18T10:08:32Z

Reviewed by: alexbl, clsung, pav

- Ask the first Python installed to install the bin/python link,

2009-07-14T09:29:03Z

and be the default Python version PR: ports/109550 Submitted by: David Yeske Obtained from: tmclaugh

- Remove regression-test target since it is not quite useful here

2009-07-02T01:51:07Z

- Honor EXAMPLESDIR, DATADIR and NOPORTEXAMPLES, NOPORTDATA

2009-07-02T01:46:33Z

- Remove bsddb module in pkg-message since it's removed from Python default modules (python3 user should use databases/py-bsddb3) - Fix WITH_UCS4 support - Mark jobs safe - Makefile/patch cleanup PR: ports/133440 Submitted by: Paul Hoffman

- Update python30 to 3.0.1

2009-03-09T22:52:21Z

Release Changelog: http://python.org/download/releases/3.0.1/NEWS.txt

Welcome to the new era of Python 3, with antigravity support!

2008-12-04T11:21:22Z

Update to Python 3.0.

Remove "_gdbm" module from packaging which should be excluded in

2008-10-13T09:50:53Z

this port. Reported by: QAT

Introduce two new versions of Python: 2.6 and 3.0rc1 (finally!)

2008-10-13T08:23:00Z

Python 2.6 will be the next default python version when enough testings of consumer ports are done. The new "2to3" program is renamed to 2to3-2.6 and 2to3-3.0 for each version, respectively. Repo-copied by: marcus

- Security fixes

2008-09-08T00:14:06Z

Multiple vulnerabilities: 1) Various integer overflow errors exist in core modules e.g. stringobject, unicodeobject, bufferobject, longobject, tupleobject, stropmodule, gcmodule, mmapmodule. 2) An integer overflow in the hashlib module can lead to an unreliable cryptographic digest results. 3) Integer overflow errors in the processing of unicode strings can be exploited to cause buffer overflows on 32-bit systems. 4) An integer overflow exists in the PyOS_vsnprintf() function on architectures that do not have a "vsnprintf()" function. 5) An integer underflow error in the PyOS_vsnprintf() function when passing zero-length strings can lead to memory corruption. PR: 127172 (based on) Submitted by: bf Obtained from: python svn Security: CVE-2008-2315, CVE-2008-2316, CVE-2008-3142, CVE-2008-3144, CVE-2008-3143. (vuxml come later)

Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.

2008-08-21T06:18:49Z

Specifically, newer autoconf (> 2.13) has different semantic of the configure target. In short, one should use --build=CONFIGURE_TARGET instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning and the old semantic may be removed in later autoconf releases. To workaround this issue, many ports hack the CONFIGURE_TARGET variable so that it contains the ``--build='' prefix. To solve this issue, under the fact that some ports still have configure script generated by the old autoconf, we use runtime detection in the do-configure target so that the proper argument can be used. Changes to Mk/*: - Add runtime detection magic in bsd.port.mk - Remove CONFIGURE_TARGET hack in various bsd.*.mk - USE_GNOME=gnometarget is now an no-op Changes to individual ports, other than removing the CONFIGURE_TARGET hack: = pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables) - comms/gnuradio - science/abinit - science/elmer-fem - science/elmer-matc - science/elmer-meshgen2d - science/elmerfront - science/elmerpost = use x86_64 as ARCH - devel/g-wrap = other changes - print/magicfilter GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf Total # of ports modified: 1,027 Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes) PR: 126524 (obsoletes 52917) Submitted by: rafan Tested on: two pointyhat 7-amd64 exp runs (by pav) Approved by: portmgr (pav)