NOTICE: This package has been removed from pkgsrc

./lang/python15, Interpreted, interactive, object-oriented programming language

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ]

Branch: CURRENT, Version: 1.5.2nb5, Package name: python15-1.5.2nb5, Maintainer: pkgsrc-users

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 exten-
sion language for existing applications. See the internal
documentation for hints.

Master sites:

SHA1: 2d648d07b1aa1aab32a3a24851c33715141779b9
RMD160: 25717d98fe7c01d42a78ffb08b8abc660ec2daa6
Filesize: 2473.685 KB

Version history: (Expand)

CVS history: (Expand)


   2007-02-22 20:27:30 by Thomas Klausner | Files touched by this commit (721) 
Log message:
Whitespace cleanup, courtesy of pkglint.
Patch provided by Sergey Svishchev in private mail.
   2006-07-22 02:37:56 by Min Sik Kim | Files touched by this commit (2) 
Log message:
Fix PLIST on Linux.  Bump PKGREVISION.
   2006-07-22 02:36:19 by Min Sik Kim | Files touched by this commit (1) 
Log message:
Fix a replace-interpreter error.  PKGREVISION will be bumped shortly
after PLIST changes for Linux.
   2006-07-09 01:11:17 by Johnny C. Lam | Files touched by this commit (877) 
Log message:
Change the format of BUILDLINK_ORDER to contain depth information as well,
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.

For example, "make show-buildlink3" in fonts/Xft2 displays:

	zlib
	fontconfig
	    iconv
	    zlib
	    freetype2
	    expat
	freetype2
	Xrender
	    renderproto
   2006-07-09 00:39:49 by Johnny C. Lam | Files touched by this commit (877) 
Log message:
Track information in a new variable BUILDLINK_ORDER that informs us
of the order in which buildlink3.mk files are (recursively) included
by a package Makefile.
   2006-04-12 12:27:47 by Roland Illig | Files touched by this commit (749) 
Log message:
Aligned the last line of the buildlink3.mk files with the first line, so
that they look nicer.
   2006-04-06 08:23:06 by Jeremy C. Reed | Files touched by this commit (1147) 
Log message:
Over 1200 files touched but no revisions bumped :)

RECOMMENDED is removed. It becomes ABI_DEPENDS.

BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.

BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.

BUILDLINK_DEPENDS does not change.

IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".

Added to obsolete.mk checking for IGNORE_RECOMMENDED.

I did not manually go through and fix any aesthetic tab/spacing issues.

I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.

I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.

As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.

As discussed on tech-pkg.

I will commit to revbump, pkglint, pkg_install, createbuildlink separately.

Note that if you use wip, it will fail!  I will commit to pkgsrc-wip
later (within day).
   2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257) 
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.