Up to [cvs.NetBSD.org] / pkgsrc / lang / python27
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.6 / (download) - annotate - [select for diffs], Fri Dec 30 10:53:21 2016 UTC (22 months, 2 weeks ago) by adam
CVS Tags: pkgsrc-2018Q3-base, pkgsrc-2018Q3, pkgsrc-2018Q2-base, pkgsrc-2018Q2, pkgsrc-2018Q1-base, pkgsrc-2018Q1, pkgsrc-2017Q4-base, pkgsrc-2017Q4, pkgsrc-2017Q3-base, pkgsrc-2017Q3, pkgsrc-2017Q2-base, pkgsrc-2017Q2, pkgsrc-2017Q1-base, pkgsrc-2017Q1, pkgsrc-, HEAD
Changes since 1.5: +2 -6 lines
Diff to previous 1.5 (colored)
Changes 2.7.13: Core and Builtins ----------------- - Issue 28847: dumbdbm no longer writes the index file in when it is not changed and supports reading read-only files. - Issue 11145: Fixed miscellaneous issues with C-style formatting of types with custom __oct__ and __hex__. - Issue 24469: Fixed memory leak caused by int subclasses without overridden tp_free (e.g. C-inherited Cython classes). - Issue 19398: Extra slash no longer added to sys.path components in case of empty compile-time PYTHONPATH components. - Issue 21720: Improve exception message when the type of fromlist is unicode. fromlist parameter of __import__() only accepts str in Python 2 and this will help to identify the problem especially when the unicode_literals future import is used. - Issue 26906: Resolving special methods of uninitialized type now causes implicit initialization of the type instead of a fail. - Issue 18287: PyType_Ready() now checks that tp_name is not NULL. Original patch by Niklas Koep. - Issue 24098: Fixed possible crash when AST is changed in process of compiling it. - Issue 28350: String constants with null character no longer interned. - Issue 27942: String constants now interned recursively in tuples and frozensets. - Issue 15578: Correctly incref the parent module while importing. - Issue 26307: The profile-opt build now applies PGO to the built-in modules. - Issue 26020: set literal evaluation order did not match documented behaviour. - Issue 27870: A left shift of zero by a large integer no longer attempts to allocate large amounts of memory. - Issue 25604: Fix a minor bug in integer true division; this bug could potentially have caused off-by-one-ulp results on platforms with unreliable ldexp implementations. - Issue 27473: Fixed possible integer overflow in str, unicode and bytearray concatenations and repetitions. Based on patch by Xiang Zhang. - Issue 27507: Add integer overflow check in bytearray.extend(). Patch by Xiang Zhang. - Issue 27581: Don't rely on wrapping for overflow check in PySequence_Tuple(). Patch by Xiang Zhang. - Issue 23908: os functions, open() and the io.FileIO constructor now reject unicode paths with embedded null character on Windows instead of silently truncating them. - Issue 27514: Make having too many statically nested blocks a SyntaxError instead of SystemError.
Revision 1.5 / (download) - annotate - [select for diffs], Mon May 7 01:53:42 2012 UTC (6 years, 6 months ago) by dholland
CVS Tags: pkgsrc-2016Q4-base, pkgsrc-2016Q4, pkgsrc-2016Q3-base, pkgsrc-2016Q3, pkgsrc-2016Q2-base, pkgsrc-2016Q2, pkgsrc-2016Q1-base, pkgsrc-2016Q1, pkgsrc-2015Q4-base, pkgsrc-2015Q4, pkgsrc-2015Q3-base, pkgsrc-2015Q3, pkgsrc-2015Q2-base, pkgsrc-2015Q2, pkgsrc-2015Q1-base, pkgsrc-2015Q1, pkgsrc-2014Q4-base, pkgsrc-2014Q4, pkgsrc-2014Q3-base, pkgsrc-2014Q3, pkgsrc-2014Q2-base, pkgsrc-2014Q2, pkgsrc-2014Q1-base, pkgsrc-2014Q1, pkgsrc-2013Q4-base, pkgsrc-2013Q4, pkgsrc-2013Q3-base, pkgsrc-2013Q3, pkgsrc-2013Q2-base, pkgsrc-2013Q2, pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4, pkgsrc-2012Q3-base, pkgsrc-2012Q3, pkgsrc-2012Q2-base, pkgsrc-2012Q2
Changes since 1.4: +2 -2 lines
Diff to previous 1.4 (colored)
Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=) It turns out there were a lot of these.
Revision 1.4 / (download) - annotate - [select for diffs], Fri Apr 22 13:42:06 2011 UTC (7 years, 6 months ago) by obache
CVS Tags: pkgsrc-2012Q1-base, pkgsrc-2012Q1, pkgsrc-2011Q4-base, pkgsrc-2011Q4, pkgsrc-2011Q3-base, pkgsrc-2011Q3, pkgsrc-2011Q2-base, pkgsrc-2011Q2
Changes since 1.3: +2 -1 lines
Diff to previous 1.3 (colored)
recursive bump from gettext-lib shlib bump.
Revision 1.3 / (download) - annotate - [select for diffs], Fri Apr 15 17:23:24 2011 UTC (7 years, 7 months ago) by drochner
Changes since 1.2: +4 -4 lines
Diff to previous 1.2 (colored)
comment out BUILDLINK_INCDIRS/BUILDLINK_LIBDIRS/BUILDLINK_TRANSFORM 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
Revision 1.2 / (download) - annotate - [select for diffs], Tue Feb 22 10:50:37 2011 UTC (7 years, 8 months ago) by adam
CVS Tags: pkgsrc-2011Q1-base, pkgsrc-2011Q1
Changes since 1.1: +3 -3 lines
Diff to previous 1.1 (colored)
Fix unprivileged build
Revision 22.214.171.124 / (download) - annotate - [select for diffs] (vendor branch), Tue Feb 22 08:52:01 2011 UTC (7 years, 8 months ago) by obache
CVS Tags: pkgsrc-base
Changes since 1.1: +0 -0 lines
Diff to previous 1.1 (colored)
Import python27-2.7.1 as lang/python27. Python 2.7 is intended to be the last major release in the 2.x series. The Python maintainers are planning to focus their future efforts on the Python 3.x series. This means that 2.7 will remain in place for a long time, running production systems that have not been ported to Python 3.x. Two consequences of the long-term significance of 2.7 are: * It's very likely the 2.7 release will have a longer period of maintenance compared to earlier 2.x versions. Python 2.7 will continue to be maintained while the transition to 3.x continues, and the developers are planning to support Python 2.7 with bug-fix releases beyond the typical two years. * A policy decision was made to silence warnings only of interest to developers. :exc:`DeprecationWarning` and its descendants are now ignored unless otherwise requested, preventing users from seeing warnings triggered by an application. This change was also made in the branch that will become Python 3.2. (Discussed on stdlib-sig and carried out in :issue:`7319`.) In previous releases, :exc:`DeprecationWarning` messages were enabled by default, providing Python developers with a clear indication of where their code may break in a future major version of Python. However, there are increasingly many users of Python-based applications who are not directly involved in the development of those applications. :exc:`DeprecationWarning` messages are irrelevant to such users, making them worry about an application that's actually working correctly and burdening application developers with responding to these concerns. You can re-enable display of :exc:`DeprecationWarning` messages by running Python with the :option:`-Wdefault <-W>` (short form: :option:`-Wd <-W>`) switch, or by setting the :envvar:`PYTHONWARNINGS` environment variable to ``"default"`` (or ``"d"``) before running Python. Python code can also re-enable them by calling ``warnings.simplefilter('default')``.
Revision 1.1 / (download) - annotate - [select for diffs], Tue Feb 22 08:52:01 2011 UTC (7 years, 8 months ago) by obache
This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.