<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pkgsrc/lang/python26/buildlink3.mk, branch pkgsrc-2014Q2</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc-2014Q2</id>
<link rel='self' href='https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc-2014Q2'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/'/>
<updated>2013-11-06T07:25:49Z</updated>
<entry>
<title>Python 2.6.9 is a security-fix source-only release for Python 2.6.8, fixing several reported security issues: issue 16037, issue 16038, issue 16039, issue 16040, issue 16041, and issue 16042 (CVE-2013-1752, long lines consuming too much memory), as well as issue 14984 (security enforcement on $HOME/.netrc files), issue 16248 (code execution vulnerability in tkinter), and issue 18709 (CVE-2013-4238, SSL module handling of NULL bytes inside subjectAltName).</title>
<updated>2013-11-06T07:25:49Z</updated>
<author>
<name>adam</name>
<email>adam@pkgsrc.org</email>
</author>
<published>2013-11-06T07:25:49Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=60043f8b7b679c9f0eb08d2ff49ed1acf8e93020'/>
<id>urn:sha1:60043f8b7b679c9f0eb08d2ff49ed1acf8e93020</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=)</title>
<updated>2012-05-07T01:53:12Z</updated>
<author>
<name>dholland</name>
<email>dholland@pkgsrc.org</email>
</author>
<published>2012-05-07T01:53:12Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=0bcdacfbcf0a1f7f4455399808295e6e6f7e01bc'/>
<id>urn:sha1:0bcdacfbcf0a1f7f4455399808295e6e6f7e01bc</id>
<content type='text'>
It turns out there were a lot of these.</content>
</entry>
<entry>
<title>recursive bump from gettext-lib shlib bump.</title>
<updated>2011-04-22T13:41:54Z</updated>
<author>
<name>obache</name>
<email>obache@pkgsrc.org</email>
</author>
<published>2011-04-22T13:41:54Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=0e2c97799a873b423fce3b9a712f48300f567461'/>
<id>urn:sha1:0e2c97799a873b423fce3b9a712f48300f567461</id>
<content type='text'>
</content>
</entry>
<entry>
<title>comment out BUILDLINK_INCDIRS/BUILDLINK_LIBDIRS/BUILDLINK_TRANSFORM</title>
<updated>2011-04-15T17:23:23Z</updated>
<author>
<name>drochner</name>
<email>drochner@pkgsrc.org</email>
</author>
<published>2011-04-15T17:23:23Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=67808816f60c9e248c799096967ed064989044ab'/>
<id>urn:sha1:67808816f60c9e248c799096967ed064989044ab</id>
<content type='text'>
definitions which do things behind the client pkgs back, in particular
manipulate the library search path
It is well possible that this causes some fallout, but I hope it
will be small and can be dealt with on a per-pkg basis.
(partly) suggested by Mark Davies on tech-pkg</content>
</entry>
<entry>
<title>bump PKGREVs for Python pkgs, as suggested by David Sainty -- at least</title>
<updated>2009-09-08T10:06:35Z</updated>
<author>
<name>drochner</name>
<email>drochner@pkgsrc.org</email>
</author>
<published>2009-09-08T10:06:35Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=a6f5aa147ff3cf1b683ce731d337a3b2c84cc812'/>
<id>urn:sha1:a6f5aa147ff3cf1b683ce731d337a3b2c84cc812</id>
<content type='text'>
on Linux one can't build some extensions against an old Python (with
spurious -ldb4 linkage) anymore
also sync the bl3 files of the non-default versions with python25
for consistency</content>
</entry>
<entry>
<title>Initial import of python26-2.6.2.</title>
<updated>2009-04-19T14:42:48Z</updated>
<author>
<name>wiz</name>
<email>wiz@pkgsrc.org</email>
</author>
<published>2009-04-19T14:42:48Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=752b874fb3d009a116bf105f631e013ce0fd40f8'/>
<id>urn:sha1:752b874fb3d009a116bf105f631e013ce0fd40f8</id>
<content type='text'>
Compiles, installs, and runs on NetBSD-5.99.10/amd64; no further
tests done. Please test and fix on your platform!

What's new in Python-2.6:

The major theme of Python 2.6 is preparing the migration path to
Python 3.0, a major redesign of the language. Whenever possible,
Python 2.6 incorporates new features and syntax from 3.0 while
remaining compatible with existing code by not removing older
features or syntax. When it tries to do what it can, adding
compatibility functions in a future_builtins module and a -3 switch
to warn about usages that will become unsupported in 3.0.

Some significant new packages have been added to the standard
library, such as the multiprocessing and json modules, but there
aren way.

Python 2.6 also sees a number of improvements and bugfixes throughout
the source. A search through the change logs finds there were 259
patches applied and 612 bugs fixed between Python 2.5 and 2.6. Both
figures are likely to be underestimates.

More details at
http://docs.python.org/whatsnew/2.6.html</content>
</entry>
</feed>
