NOTICE: This package no longer exists in Ports


./lang/python/2.6 [interpreted object-oriented programming language]

[ CVSweb ] [ Homepage ] [ RSS feed ]

Version: 2.6, Package name: Python-2.6.6
Maintained by: Damien Miller
Master sites:
Description-bsddb
Python is an interpreted, interactive, object-oriented programming
language that combines remarkable power with very clear syntax. For
an introduction to programming in Python you are referred to the
Python Tutorial. The Python Library Reference documents built-in
and standard types, constants, functions and modules. Finally, the
Python Reference Manual describes the syntax and semantics of the
core language in (perhaps too) much detail.

Python's basic power can be extended with your own modules written
in C or C++. On most systems such modules may be dynamically loaded.
Python is also adaptable as an extension language for existing
applications. See the internal documentation for hints.

This package contains the bsddb, for using the Berkeley DB library in
Python.

Description-gdbm
Python is an interpreted, interactive, object-oriented programming
language that combines remarkable power with very clear syntax. For
an introduction to programming in Python you are referred to the
Python Tutorial. The Python Library Reference documents built-in
and standard types, constants, functions and modules. Finally, the
Python Reference Manual describes the syntax and semantics of the
core language in (perhaps too) much detail.

Python's basic power can be extended with your own modules written
in C or C++. On most systems such modules may be dynamically loaded.
Python is also adaptable as an extension language for existing
applications. See the internal documentation for hints.

This package contains the gdbm, for using the GNU DBM library in
Python.

Description-idle
Python is an interpreted, interactive, object-oriented programming
language that combines remarkable power with very clear syntax. For
an introduction to programming in Python you are referred to the
Python Tutorial. The Python Library Reference documents built-in
and standard types, constants, functions and modules. Finally, the
Python Reference Manual describes the syntax and semantics of the
core language in (perhaps too) much detail.

Python's basic power can be extended with your own modules written
in C or C++. On most systems such modules may be dynamically loaded.
Python is also adaptable as an extension language for existing
applications. See the internal documentation for hints.

This package contains IDE for Python.

Description-main
Python is an interpreted, interactive, object-oriented
programming language that combines remarkable power with
very clear syntax. For an introduction to programming in
Python you are referred to the Python Tutorial. The Python
Library Reference documents built-in and standard types,
constants, functions and modules. Finally, the Python
Reference Manual describes the syntax and semantics of the
core language in (perhaps too) much detail.

Python's basic power can be extended with your own modules
written in C or C++. On most systems such modules may be
dynamically loaded. Python is also adaptable as an
extension language for existing applications. See the
internal documentation for hints.

Description-tests
Python is an interpreted, interactive, object-oriented programming
language that combines remarkable power with very clear syntax. For
an introduction to programming in Python you are referred to the
Python Tutorial. The Python Library Reference documents built-in
and standard types, constants, functions and modules. Finally, the
Python Reference Manual describes the syntax and semantics of the
core language in (perhaps too) much detail.

Python's basic power can be extended with your own modules written
in C or C++. On most systems such modules may be dynamically loaded.
Python is also adaptable as an extension language for existing
applications. See the internal documentation for hints.

This package contains the Python testsuite.

Description-tkinter
Python is an interpreted, interactive, object-oriented programming
language that combines remarkable power with very clear syntax. For
an introduction to programming in Python you are referred to the
Python Tutorial. The Python Library Reference documents built-in
and standard types, constants, functions and modules. Finally, the
Python Reference Manual describes the syntax and semantics of the
core language in (perhaps too) much detail.

Python's basic power can be extended with your own modules written
in C or C++. On most systems such modules may be dynamically loaded.
Python is also adaptable as an extension language for existing
applications. See the internal documentation for hints.

This package contains the Tkinter module, for using the tk toolkit
in Python.

Description-tools
Python is an interpreted, interactive, object-oriented programming
language that combines remarkable power with very clear syntax. For
an introduction to programming in Python you are referred to the
Python Tutorial. The Python Library Reference documents built-in
and standard types, constants, functions and modules. Finally, the
Python Reference Manual describes the syntax and semantics of the
core language in (perhaps too) much detail.

Python's basic power can be extended with your own modules written
in C or C++. On most systems such modules may be dynamically loaded.
Python is also adaptable as an extension language for existing
applications. See the internal documentation for hints.

This package contains extra tools that Python users may find useful
as well as a Python mode for Emacs.

UNMESSAGE-idle
Don't forget to remove ${PREFIX}/bin/idle
if it was a symlink to ${PREFIX}/bin/idle2.6.

UNMESSAGE-main
Don't forget to remove ${PREFIX}/bin/python,
${PREFIX}/bin/2to3, ${PREFIX}/bin/python-config or/and
${PREFIX}/bin/pydoc if they were symlinks to
${PREFIX}/bin/python2.6, ${PREFIX}/bin/python2.6-2to3,
${PREFIX}/bin/python2.6-config or to ${PREFIX}/bin/pydoc2.6.


MD5: svIJ3ycKMzFeYsH/rBk38A=
RMD160: 6Qp/+LUUUdsB+khu5r7daT6jn+8=
Filesize: 13006.394 KB

Package available on: cdrom(), ftp()
Distfile available on: cdrom(), ftp()

Version History (View Complete History)
  • (2011-07-14) Package deleted from Ports
  • (2010-09-17) Updated to version: Python-2.6.6
  • (2010-07-23) Updated to version: Python-2.6.5
  • (2009-10-16) Updated to version: Python-2.6.3
  • (2009-05-04) Updated to version: Python-2.6.2
  • (2009-01-02) Updated to version: Python-2.6.1
  • (2008-10-21) Package added to openports.se, version Python-2.6 (created)
[show/hide] View available PLISTS (Can be a lot of data)

CVS Commit History:

   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-13 02:03:32 by Jasper Lievisse Adriaanse | Files touched by this commit (45)
Log message:
Retire this version of the 2.x family. All ports either use the
default (2.7) or are using an even older version (2.4/2.5) so 2.6 can go.
ok sthen@ rpointel@
   2011-07-08 01:39:37 by Jasper Lievisse Adriaanse | Files touched by this commit (2)
Log message:
fix, as spotted by nigel taylor
   2011-07-08 01:39:37 by Jasper Lievisse Adriaanse | Files touched by this commit (2)
Log message:
fix, as spotted by nigel taylor
   2011-07-06 06:25:29 by Jasper Lievisse Adriaanse | Files touched by this commit (3)
Log message:
regen
   2011-05-30 15:11:44 by Remi Pointel | Files touched by this commit (8)
Log message:
Correct the wrong value of LDFLAGS (certain ports will need WANTLIB += ${MODPY_WANTLIB}).
Thanks for fgsch@ for his patch-Modules_selectmodule_c to correct SIGBUS error on sparc64 (test_kqueue.py).
It's time make bulks of Python2.7 on as many archs as we can.
Thanks a lot.
ok sthen@ aja@
   2011-05-30 15:11:44 by Remi Pointel | Files touched by this commit (8)
Log message:
Correct the wrong value of LDFLAGS (certain ports will need WANTLIB += ${MODPY_WANTLIB}).
Thanks for fgsch@ for his patch-Modules_selectmodule_c to correct SIGBUS error on sparc64 (test_kqueue.py).
It's time make bulks of Python2.7 on as many archs as we can.
Thanks a lot.
ok sthen@ aja@
   2011-05-23 00:42:02 by Jasper Lievisse Adriaanse | Files touched by this commit (7)
Log message:
Remove python-mode.el, it's now part of the emacs-python package.
It wasn't distributed anymore in the python distfile starting from 2.7 anymore.
Please install the emacs-python pacakge to continue using the functionality.
ok rpointel@
   2011-05-23 00:42:02 by Jasper Lievisse Adriaanse | Files touched by this commit (7)
Log message:
Remove python-mode.el, it's now part of the emacs-python package.
It wasn't distributed anymore in the python distfile starting from 2.7 anymore.
Please install the emacs-python pacakge to continue using the functionality.
ok rpointel@
   2011-05-23 00:42:02 by Jasper Lievisse Adriaanse | Files touched by this commit (7)
Log message:
Remove python-mode.el, it's now part of the emacs-python package.
It wasn't distributed anymore in the python distfile starting from 2.7 anymore.
Please install the emacs-python pacakge to continue using the functionality.
ok rpointel@
   2011-05-03 11:17:01 by Federico G. Schwindt | Files touched by this commit (8)
Log message:
- install 2to3 under python2.6-2to3 so it can co-exist with 2.7
- use right autoconf version
- fix CVE-2011-1521 (2.4 and 2.5 will be handled separately)
- bump
rpointel sthen martynas ok.
   2011-05-03 11:17:01 by Federico G. Schwindt | Files touched by this commit (8)
Log message:
- install 2to3 under python2.6-2to3 so it can co-exist with 2.7
- use right autoconf version
- fix CVE-2011-1521 (2.4 and 2.5 will be handled separately)
- bump
rpointel sthen martynas ok.
   2011-05-03 11:17:01 by Federico G. Schwindt | Files touched by this commit (8)
Log message:
- install 2to3 under python2.6-2to3 so it can co-exist with 2.7
- use right autoconf version
- fix CVE-2011-1521 (2.4 and 2.5 will be handled separately)
- bump
rpointel sthen martynas ok.
   2011-05-03 11:17:01 by Federico G. Schwindt | Files touched by this commit (8)
Log message:
- install 2to3 under python2.6-2to3 so it can co-exist with 2.7
- use right autoconf version
- fix CVE-2011-1521 (2.4 and 2.5 will be handled separately)
- bump
rpointel sthen martynas ok.
   2011-05-03 11:17:01 by Federico G. Schwindt | Files touched by this commit (8)
Log message:
- install 2to3 under python2.6-2to3 so it can co-exist with 2.7
- use right autoconf version
- fix CVE-2011-1521 (2.4 and 2.5 will be handled separately)
- bump
rpointel sthen martynas ok.
   2011-05-03 11:17:01 by Federico G. Schwindt | Files touched by this commit (8)
Log message:
- install 2to3 under python2.6-2to3 so it can co-exist with 2.7
- use right autoconf version
- fix CVE-2011-1521 (2.4 and 2.5 will be handled separately)
- bump
rpointel sthen martynas ok.
   2011-05-03 11:17:01 by Federico G. Schwindt | Files touched by this commit (8)
Log message:
- install 2to3 under python2.6-2to3 so it can co-exist with 2.7
- use right autoconf version
- fix CVE-2011-1521 (2.4 and 2.5 will be handled separately)
- bump
rpointel sthen martynas ok.
   2011-05-03 11:17:01 by Federico G. Schwindt | Files touched by this commit (8)
Log message:
- install 2to3 under python2.6-2to3 so it can co-exist with 2.7
- use right autoconf version
- fix CVE-2011-1521 (2.4 and 2.5 will be handled separately)
- bump
rpointel sthen martynas ok.
   2011-04-12 13:28:13 by Matthias Kilian | Files touched by this commit (7)
Log message:
Whenever a package installs a script using #!/usr/bin/env, god kills
a kitten.
Let pydoc${VERSION} use #!${LOCALBASE}/bin/python${VERSION} instead
of $!/usr/bin/env python${VERSION}.
ok rpointel@, sthen@ (after some discussion wether post-build is
the proper target for this or not)
   2011-04-12 13:28:13 by Matthias Kilian | Files touched by this commit (7)
Log message:
Whenever a package installs a script using #!/usr/bin/env, god kills
a kitten.
Let pydoc${VERSION} use #!${LOCALBASE}/bin/python${VERSION} instead
of $!/usr/bin/env python${VERSION}.
ok rpointel@, sthen@ (after some discussion wether post-build is
the proper target for this or not)
   2010-11-15 13:55:25 by Stuart Henderson | Files touched by this commit (7)
Log message:
use tk.port.mk and move -tkinter to a more recent version of Tcl/Tk.
reads fine to fgsch@
   2010-11-15 13:55:25 by Stuart Henderson | Files touched by this commit (7)
Log message:
use tk.port.mk and move -tkinter to a more recent version of Tcl/Tk.
reads fine to fgsch@
   2010-10-28 02:22:11 by Federico G. Schwindt | Files touched by this commit (4)
Log message:
Simplify and switch to REVISION.
From Alexandr Shadchin (firstname dot lastname at gmail dot com).
martynas@ ok.
   2010-10-18 13:20:42 by Marc Espie | Files touched by this commit (54)
Log message:
USE_GROFF=Yes
   2010-09-22 07:44:12 by Jasper Lievisse Adriaanse | Files touched by this commit (3)
Log message:
- remove the BROKEN-mips64 markers after miod's recent softfloat commit,
python seems to be working well enough now.
   2010-09-16 16:36:08 by Federico G. Schwindt | Files touched by this commit (9)
Log message:
Update Python to 2.6.6. Tested by many.
sthen@ ok
   2010-09-16 16:36:08 by Federico G. Schwindt | Files touched by this commit (9)
Log message:
Update Python to 2.6.6. Tested by many.
sthen@ ok
   2010-09-16 16:36:08 by Federico G. Schwindt | Files touched by this commit (9)
Log message:
Update Python to 2.6.6. Tested by many.
sthen@ ok
   2010-09-16 16:36:08 by Federico G. Schwindt | Files touched by this commit (9)
Log message:
Update Python to 2.6.6. Tested by many.
sthen@ ok
   2010-09-16 16:36:08 by Federico G. Schwindt | Files touched by this commit (9)
Log message:
Update Python to 2.6.6. Tested by many.
sthen@ ok
   2010-09-16 16:36:08 by Federico G. Schwindt | Files touched by this commit (9)
Log message:
Update Python to 2.6.6. Tested by many.
sthen@ ok
   2010-09-16 16:36:08 by Federico G. Schwindt | Files touched by this commit (9)
Log message:
Update Python to 2.6.6. Tested by many.
sthen@ ok
   2010-09-16 16:36:08 by Federico G. Schwindt | Files touched by this commit (9)
Log message:
Update Python to 2.6.6. Tested by many.
sthen@ ok
   2010-09-16 16:36:08 by Federico G. Schwindt | Files touched by this commit (9)
Log message:
Update Python to 2.6.6. Tested by many.
sthen@ ok
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-07-23 07:56:26 by Stuart Henderson | Files touched by this commit (11)
Log message:
Update Python to 2.6.5, committing on behalf of fgsch@ whose laptop is broken.
   2010-04-15 12:35:02 by Jasper Lievisse Adriaanse | Files touched by this commit (4)
Log message:
- more BROKEN-$ARCH
   2010-04-15 08:58:25 by Antoine Jacoutot | Files touched by this commit (55)
Log message:
Stupid poor blank lines, stupid poor blank lines...
   2010-04-15 08:58:25 by Antoine Jacoutot | Files touched by this commit (55)
Log message:
Stupid poor blank lines, stupid poor blank lines...
   2010-04-15 08:11:02 by Antoine Jacoutot | Files touched by this commit (64)
Log message:
Consistency: remove the 1, 2 or even 3 empty blank lines.
sthen@ agrees
   2010-04-15 08:11:02 by Antoine Jacoutot | Files touched by this commit (64)
Log message:
Consistency: remove the 1, 2 or even 3 empty blank lines.
sthen@ agrees
   2010-02-25 04:02:39 by Peter Hessler | Files touched by this commit (11)
Log message:
Allow Python to build on loongson.  Bring in some libffi fixes, inspired
by jasper@'s fixes to the libffi port.
Mark mips64 (aka, sgi) as BROKEN, as the build fails.  We'll look closer
at this after unlock.
OK jasper@
ports is unlocked for a while only for those who have been informed.
   2010-02-25 04:02:39 by Peter Hessler | Files touched by this commit (11)
Log message:
Allow Python to build on loongson.  Bring in some libffi fixes, inspired
by jasper@'s fixes to the libffi port.
Mark mips64 (aka, sgi) as BROKEN, as the build fails.  We'll look closer
at this after unlock.
OK jasper@
ports is unlocked for a while only for those who have been informed.
   2010-02-25 04:02:39 by Peter Hessler | Files touched by this commit (11)
Log message:
Allow Python to build on loongson.  Bring in some libffi fixes, inspired
by jasper@'s fixes to the libffi port.
Mark mips64 (aka, sgi) as BROKEN, as the build fails.  We'll look closer
at this after unlock.
OK jasper@
ports is unlocked for a while only for those who have been informed.
   2010-02-25 04:02:39 by Peter Hessler | Files touched by this commit (11)
Log message:
Allow Python to build on loongson.  Bring in some libffi fixes, inspired
by jasper@'s fixes to the libffi port.
Mark mips64 (aka, sgi) as BROKEN, as the build fails.  We'll look closer
at this after unlock.
OK jasper@
ports is unlocked for a while only for those who have been informed.
   2010-02-09 05:23:59 by Jasper Lievisse Adriaanse | Files touched by this commit (19)
Log message:
- extend archtecture tests for mips64el
ok naddy@ phessler@
   2010-01-20 01:15:21 by Marc Espie | Files touched by this commit (6)
Log message:
fix update from OpenBSD 4.5 (missed @pkgpath markers at the time
-bz2, -expat, -sqlite were removed)
   2010-01-20 01:15:21 by Marc Espie | Files touched by this commit (6)
Log message:
fix update from OpenBSD 4.5 (missed @pkgpath markers at the time
-bz2, -expat, -sqlite were removed)
   2009-11-22 15:53:19 by Jasper Lievisse Adriaanse | Files touched by this commit (5)
Log message:
- minor tweaks for mips64, none of the versions fully build, but at least
they're somewhat getting there.
- with the added patch, 2.5 gets as far as 2.6, and then fails terribly.
ok djm@ (MAINTAINER)
   2009-10-27 17:35:09 by Stuart Henderson | Files touched by this commit (7)
Log message:
fix @conflict lines; unbreaks pkg_add -u if you have python-foo-2.6
installed (with the new version of pkg_add). ok djm@.
   2009-10-27 17:35:09 by Stuart Henderson | Files touched by this commit (7)
Log message:
fix @conflict lines; unbreaks pkg_add -u if you have python-foo-2.6
installed (with the new version of pkg_add). ok djm@.
   2009-10-27 17:35:09 by Stuart Henderson | Files touched by this commit (7)
Log message:
fix @conflict lines; unbreaks pkg_add -u if you have python-foo-2.6
installed (with the new version of pkg_add). ok djm@.
   2009-10-27 17:35:09 by Stuart Henderson | Files touched by this commit (7)
Log message:
fix @conflict lines; unbreaks pkg_add -u if you have python-foo-2.6
installed (with the new version of pkg_add). ok djm@.
   2009-10-27 17:35:09 by Stuart Henderson | Files touched by this commit (7)
Log message:
fix @conflict lines; unbreaks pkg_add -u if you have python-foo-2.6
installed (with the new version of pkg_add). ok djm@.
   2009-10-27 17:35:09 by Stuart Henderson | Files touched by this commit (7)
Log message:
fix @conflict lines; unbreaks pkg_add -u if you have python-foo-2.6
installed (with the new version of pkg_add). ok djm@.
   2009-10-27 17:35:09 by Stuart Henderson | Files touched by this commit (7)
Log message:
fix @conflict lines; unbreaks pkg_add -u if you have python-foo-2.6
installed (with the new version of pkg_add). ok djm@.
   2009-10-16 03:38:20 by Damien Miller | Files touched by this commit (9)
Log message:
update to maintenance release 2.6.3, relnotes at:
http://www.python.org/download/releases/2.6.3/NEWS.txt
NB. regress tests are known to fail if py-xml is installed. Try to spend
less time than I did in figuring this out.
   2009-10-16 03:38:20 by Damien Miller | Files touched by this commit (9)
Log message:
update to maintenance release 2.6.3, relnotes at:
http://www.python.org/download/releases/2.6.3/NEWS.txt
NB. regress tests are known to fail if py-xml is installed. Try to spend
less time than I did in figuring this out.
   2009-10-16 03:38:20 by Damien Miller | Files touched by this commit (9)
Log message:
update to maintenance release 2.6.3, relnotes at:
http://www.python.org/download/releases/2.6.3/NEWS.txt
NB. regress tests are known to fail if py-xml is installed. Try to spend
less time than I did in figuring this out.
   2009-10-16 03:38:20 by Damien Miller | Files touched by this commit (9)
Log message:
update to maintenance release 2.6.3, relnotes at:
http://www.python.org/download/releases/2.6.3/NEWS.txt
NB. regress tests are known to fail if py-xml is installed. Try to spend
less time than I did in figuring this out.
   2009-10-16 03:38:20 by Damien Miller | Files touched by this commit (9)
Log message:
update to maintenance release 2.6.3, relnotes at:
http://www.python.org/download/releases/2.6.3/NEWS.txt
NB. regress tests are known to fail if py-xml is installed. Try to spend
less time than I did in figuring this out.
   2009-10-16 03:38:20 by Damien Miller | Files touched by this commit (9)
Log message:
update to maintenance release 2.6.3, relnotes at:
http://www.python.org/download/releases/2.6.3/NEWS.txt
NB. regress tests are known to fail if py-xml is installed. Try to spend
less time than I did in figuring this out.
   2009-10-16 03:38:20 by Damien Miller | Files touched by this commit (9)
Log message:
update to maintenance release 2.6.3, relnotes at:
http://www.python.org/download/releases/2.6.3/NEWS.txt
NB. regress tests are known to fail if py-xml is installed. Try to spend
less time than I did in figuring this out.
   2009-10-16 03:38:20 by Damien Miller | Files touched by this commit (9)
Log message:
update to maintenance release 2.6.3, relnotes at:
http://www.python.org/download/releases/2.6.3/NEWS.txt
NB. regress tests are known to fail if py-xml is installed. Try to spend
less time than I did in figuring this out.
   2009-10-16 03:38:20 by Damien Miller | Files touched by this commit (9)
Log message:
update to maintenance release 2.6.3, relnotes at:
http://www.python.org/download/releases/2.6.3/NEWS.txt
NB. regress tests are known to fail if py-xml is installed. Try to spend
less time than I did in figuring this out.
   2009-08-10 11:31:07 by Matthias Kilian | Files touched by this commit (19)
Log message:
WANTLIB changes after xcb addition and bump.
For some unknown reason, I forgot to commit lang/*
this morning.
   2009-06-24 19:49:54 by Jolan Luff | Files touched by this commit (5)
Log message:
avoid conflict in -tools subpackage
   2009-06-24 19:49:54 by Jolan Luff | Files touched by this commit (5)
Log message:
avoid conflict in -tools subpackage
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-05-03 16:26:27 by Damien Miller | Files touched by this commit (13)
Log message:
python-2.6.2
   2009-03-16 05:40:25 by Marc Espie | Files touched by this commit (5)
Log message:
a few deps
   2009-01-01 14:03:28 by Damien Miller | Files touched by this commit (71)
Log message:
Updates and garbage collect all three Python ports:
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
   2009-01-01 14:03:28 by Damien Miller | Files touched by this commit (71)
Log message:
Updates and garbage collect all three Python ports:
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
   2009-01-01 14:03:28 by Damien Miller | Files touched by this commit (71)
Log message:
Updates and garbage collect all three Python ports:
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
   2009-01-01 14:03:28 by Damien Miller | Files touched by this commit (71)
Log message:
Updates and garbage collect all three Python ports:
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
   2009-01-01 14:03:28 by Damien Miller | Files touched by this commit (71)
Log message:
Updates and garbage collect all three Python ports:
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
   2009-01-01 14:03:28 by Damien Miller | Files touched by this commit (71)
Log message:
Updates and garbage collect all three Python ports:
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
   2009-01-01 14:03:28 by Damien Miller | Files touched by this commit (71)
Log message:
Updates and garbage collect all three Python ports:
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
   2009-01-01 14:03:28 by Damien Miller | Files touched by this commit (71)
Log message:
Updates and garbage collect all three Python ports:
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
   2009-01-01 14:03:28 by Damien Miller | Files touched by this commit (71)
Log message:
Updates and garbage collect all three Python ports:
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
   2009-01-01 14:03:28 by Damien Miller | Files touched by this commit (71)
Log message:
Updates and garbage collect all three Python ports:
2.4.4 => 2.4.8
2.5.2 => 2.5.4
2.6 => 2.6.1
Python 2.4 and 2.5 lose their build knobs to match 2.6.
Removes no longer needed Python 2.5 security patches backported
from the release25-maint SVN branch.
Remove the -bz2 subpackage from all three versions. It is silly
to make a subpackage to avoid depending on something tiny and
compatibly licensed.
Python 2.4 and 2.5 lose their -expat subpackages; expat has been
in base for some time.
Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny,
compatibly licensed and is depended upon by more and more
applications. This brings it into line with the 2.6 version.
Rework all three version's handling of setup.py. Rather than regex
replacing LOCALBASE and X11BASE into setup.py post-configure, these
are passed in though environment variables. Will save hours of
frustrated cursing familiar to anyone who has accidently used the
update-patches target after configure and had to go back and redo
all the substitutions.
Rework the patching of setup.py for 2.4 and 2.5 to be more like
what we do for 2.6. I.e. keep the diff minimal and avoid deleting
huge blocks of code, so the diff has a chance of applying without
massive hand-editing each patch release.
Fix .py paths in installed .pyc files (patch from eric@)
feedback from several, particularly eric@, ajacoutot@ and Ingo
Schwarze; "get it in" ajacoutot@
   2008-12-15 22:31:32 by Damien Miller | Files touched by this commit (2)
Log message:
more unused files; spotted by fgsch@
   2008-12-15 22:31:32 by Damien Miller | Files touched by this commit (2)
Log message:
more unused files; spotted by fgsch@
   2008-12-15 15:10:34 by Damien Miller | Files touched by this commit (1)
Log message:
the python-2.6 port does not have a sqlite subpackage, so this file
is unused