Upstream changes:
0.054 2018-01-29 T. R. Wyant
Add support for (+script_run:...). This is an experimental feature
added in Perl 5.27.8. It imposes on any matches it contains the
additional restriction that everything matched has to belong to the
same Unicode script. This support will be retracted if the
functionality does not make it into Perl 5.28.
Add method scontent(). This returns significant content only. That
is, if called on the parse of '/ f u b a r /x', it returns
'/fubar/x'.
Changelog:
mdds 1.3.1
* flat_segment_tree
* fixed a bug that caused an assertion error when inserting a
out-of-bound segment whose start value equals the max key value.
mdds 1.3.0
* multi_type_vector
* changed the primary block array storage to remove additional
indirection, for improved memory locality.
Pytest 3.4.0
Deprecations and Removals
- All pytest classes now subclass object for better Python 2/3 compatibility.
This should not affect user code except in very rare edge cases.
Features
- Introduce empty_parameter_set_mark ini option to select which mark to
apply when @pytest.mark.parametrize is given an empty set of parameters.
Valid options are skip (default) and xfail. Note that it is planned
to change the default to xfail in future releases as this is considered
less error prone.
- **Incompatible change**: after community feedback the logging
<https://docs.pytest.org/en/latest/logging.html>_ functionality has
undergone some changes. Please consult the logging documentation
<https://docs.pytest.org/en/latest/logging.html#incompatible-changes-in-pytest-3-4>_
for details.
- Console output falls back to "classic" mode when capturing is disabled (-s),
otherwise the output gets garbled to the point of being useless.
- New pytest_runtest_logfinish
<https://docs.pytest.org/en/latest/writing_plugins.html#_pytest.hookspec.pytest_runtest_logfinish>_
hook which is called when a test item has finished executing, analogous to
pytest_runtest_logstart
<https://docs.pytest.org/en/latest/writing_plugins.html#_pytest.hookspec.pytest_runtest_start>_.
- Improve performance when collecting tests using many fixtures.
- New caplog.get_records(when) method which provides access to the captured
records for the "setup", "call" and "teardown"
testing stages.
- New fixture record_xml_attribute that allows modifying and inserting
attributes on the <testcase> xml node in JUnit reports.
- The default cache directory has been renamed from .cache to
.pytest_cache after community feedback that the name .cache did not
make it clear that it was used by pytest.
- Colorize the levelname column in the live-log output.
Bug Fixes
- Fix hanging pexpect test on MacOS by using flush() instead of wait().
- Fix restoring Python state after in-process pytest runs with the
pytester plugin; this may break tests using multiple inprocess
pytest runs if later ones depend on earlier ones leaking global interpreter
changes.
- Fix skipping plugin reporting hook when test aborted before plugin setup
hook.
- Fix progress percentage reported when tests fail during teardown.
- **Incompatible change**: -o/--override option no longer eats all the
remaining options, which can lead to surprising behavior: for example,
pytest -o foo=1 /path/to/test.py would fail because /path/to/test.py
would be considered as part of the -o command-line argument. One
consequence of this is that now multiple configuration overrides need
multiple -o flags: pytest -o foo=1 -o bar=2.
4.3.0:
- Fixed 557: force_alphabetical_sort and force_sort_within_sections can now be utilized together without extra new lines
- Fix case-sensitive path existence check in Mac OS X
- Added --no-lines-before for more granular control over section output
- Fixed 493: Unwanted conversion to Windows line endings
- Implemented --version-number to retrieve just the version number without the isort logo
- Breaking changes
- Python 2.7+ only (dropped 2.6) allowing various code simplifications and improvements.
3.44.24:
This release fixes dependency information when installing Hypothesis from a binary "wheel" distribution.
The install_requires for enum34 is resolved at install time, rather than at build time (with potentially different results).
Django has fixed their python_requires for versions 2.0.0 onward, simplifying Python2-compatible constraints for downstream projects.
Changes since 2.6.0beta1:
[2018-01-29] — Xdebug 2.6.0
Fixed bugs
Fixed bug #1522: Remote debugging test failures on s390 (Big Endian).
[2018-01-23] — Xdebug 2.6.0RC2
Fixed bugs
Fixed bug #1521: xdebug_gc_stats.* missing from 2.6.0RC1 tarball.
[2018-01-22] — Xdebug 2.6.0RC1
Added features
Fixed bug #1506: Add garbage collection statistics feature (Benjamin Eberlei).
Fixed bug #1507: Add functions to access Zend Engine garbage collection metrics (Benjamin Eberlei).
Improvements
Fixed bug #1510: Change switch/case "break intentionally missing" comments to use GCC 7's new "fallthrough" attribute.
Fixed bug #1511: Detect and use compiler flags through new configure option.
Fixed bugs
Fixed bug #1335: Debugging with PhpStorm sometimes gives "can not get property".
Fixed bug #1454: Invalid memory read or segfaults from a __call() method.
Fixed bug #1508: Code coverage filter not checked in xdebug_common_assign_dim handler.
Fixed bug #1509: Code coverage missing for case inside switch with PHP 7.2.
Fixed bug #1512: Xdebug does not properly encode and escape properties with quotes and \0 characters.
Fixed bug #1514: Variable names with a NULL char are cut off at NULL char.
Fixed bug #1515: Object property names with a NULL char are cut off at NULL char.
Fixed bug #1516: Can't fetch variables or object properties which have \0 characters in them.
Fixed bug #1517: Notifications incorrectly specify the error type in "type_string" instead of "type".
local changes: use plist var for gcore.
XXX don't install gcore.1 that doesn't appear to be installed but exists
remove merged patches.
GDB 8.1 includes the following changes and enhancements:
* Breakpoints on C++ functions are now set on all scopes by default
("wild" matching);
* Support for inserting breakpoints on functions marked with C++ ABI tags;
* Target floating-point arithmetic emulation during expression evaluation
(requires MPFR 3.1 or later);
* Various Python Scripting enhancements;
* Improved Rust support; in particular, Trait objects can now be inspected
when debugging Rust code;
* GDB no longer makes assumptions about the type of symbols without
debugging information to avoid producing erroneous and often confusing
results;
* The 'enable' and 'disable' commands now accept a range of breakpoint
locations;
* New 'starti' command to start the program at the first instruction;
* New 'rbreak' command to insert a number of breakpoints via a regular
expression pattern (requires Python);
* The 'ptype' command now supports printing the offset and size of
the fields in a struct;
* The 'gcore' command now supports dumping all the memory mappings
('-a' command-line option);
* New shortcuts for TUI Single-Key mode: 'i' for stepi, and 'o' for nexti;
* GDBserver enhancements:
** Support for transmitting environment variables to GDBserver;
** Support for starting inferior processes with a specified initial
working directory;
** On Unix systems, support for globbing expansion and variable
substitution of inferior command-line arguments;
* Various completion enhancements;
* The command used to compile and inject code with the 'compile' command
is now configurable;
* New '--readnever' command-line option to speed the GDB startup when
debugging information is not needed;
* Support for the following new native configurations:
** FreeBSD/aarch64 (aarch64*-*-freebsd*);
** FreeBSD/arm (arm*-*-freebsd*);
* Support for the following new targets:
** FreeBSD/aarch64 (aarch64*-*-freebsd*);
** FreeBSD/arm (arm*-*-freebsd*);
** OpenRISC ELF (or1k*-*-elf)
* Removed support for the following targets and native configurations:
** Solaris2/x86 (i?86-*-solaris2.[0-9]);
** Solaris2/sparc (sparc*-*-solaris2.[0-9]);
For a complete list and more details on each item, please see the gdb/NEWS
file, available at:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gdb/NEWS;hb=gdb-8.1-release
2.1:
ENH: Add support for Python 3.5 coroutines
ENH: Documentation updates
ENH: CI for most recent Python versions (3.5, 3.6, 3.6-dev, 3.7-dev, nightly)
ENH: Add timer unit argument for output time granularity spec
ccache 3.3.6
New features and improvements
- Improved instructions on how to get cache hits between different working
directories.
Bug fixes
- Fixed regression in ccache 3.3.5 related to the `UNCACHED_ERR_FD` feature.
3.13.0 adds support for larger processes and programs, solidifies and improves
support on existing platforms, and provides new heap-use reporting facilities.
Release 3.13.0 (15 June 2017)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3.13.0 is a feature release with many improvements and the usual collection of
bug fixes.
This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
X86/Solaris, AMD64/Solaris and AMD64/MacOSX 10.12.
* ==================== CORE CHANGES ===================
* The translation cache size has been increased to keep up with the demands of
large applications. The maximum number of sectors has increased from 24 to
48. The default number of sectors has increased from 16 to 32 on all
targets except Android, where the increase is from 6 to 12.
* The amount of memory that Valgrind can use has been increased from 64GB to
128GB. In particular this means your application can allocate up to about
60GB when running on Memcheck.
* Valgrind's default load address has been changed from 0x3800'0000 to
0x5800'0000, so as to make it possible to load larger executables. This
should make it possible to load executables of size at least 1200MB.
* A massive spaceleak caused by reading compressed debuginfo files has been
fixed. Valgrind should now be entirely usable with gcc-7.0 "-gz" created
debuginfo.
* The C++ demangler has been updated.
* Support for demangling Rust symbols has been added.
* A new representation of stack traces, the "XTree", has been added. An XTree
is a tree of stacktraces with data associated with the stacktraces. This is
used by various tools (Memcheck, Helgrind, Massif) to report on the heap
consumption of your program. Reporting is controlled by the new options
--xtree-memory=none|allocs|full and --xtree-memory-file=<file>.
A report can also be produced on demand using the gdbserver monitor command
'xtmemory [<filename>]>'. The XTree can be output in 2 formats: 'callgrind
format' and 'massif format. The existing visualisers for these formats (e.g.
callgrind_annotate, KCachegrind, ms_print) can be used to visualise and
analyse these reports.
Memcheck can also produce XTree leak reports using the Callgrind file
format. For more details, see the user manual.
* ================== PLATFORM CHANGES =================
* ppc64: support for ISA 3.0B and various fixes for existing 3.0 support
* amd64: fixes for JIT failure problems on long AVX2 code blocks
* amd64 and x86: support for CET prefixes has been added
* arm32: a few missing ARMv8 instructions have been implemented
* arm64, mips64, mips32: an alternative implementation of Load-Linked and
Store-Conditional instructions has been added. This is to deal with
processor implementations that implement the LL/SC specifications strictly
and as a result cause Valgrind to hang in certain situations. The
alternative implementation is automatically enabled at startup, as required.
You can use the option --sim-hints=fallback-llsc to force-enable it if you
want.
* Support for OSX 10.12 has been improved.
* On Linux, clone handling has been improved to honour CLONE_VFORK that
involves a child stack. Note however that CLONE_VFORK | CLONE_VM is handled
like CLONE_VFORK (by removing CLONE_VM), so applications that depend on
CLONE_VM exact semantics will (still) not work.
* The TileGX/Linux port has been removed because it appears to be both unused
and unsupported.
* ==================== TOOL CHANGES ====================
* Memcheck:
- Memcheck should give fewer false positives when running optimised
Clang/LLVM generated code.
- Support for --xtree-memory and 'xtmemory [<filename>]>'.
- New command line options --xtree-leak=no|yes and --xtree-leak-file=<file>
to produce the end of execution leak report in a xtree callgrind format
file.
- New option 'xtleak' in the memcheck leak_check monitor command, to produce
the leak report in an xtree file.
* Massif:
- Support for --xtree-memory and 'xtmemory [<filename>]>'.
- For some workloads (typically, for big applications), Massif memory
consumption and CPU consumption has decreased significantly.
* Helgrind:
- Support for --xtree-memory and 'xtmemory [<filename>]>'.
- addition of client request VALGRIND_HG_GNAT_DEPENDENT_MASTER_JOIN, useful
for Ada gnat compiled applications.
Version 2.4.3 - 12/Sep/2017
- Fixed display of pathnames in `luarocks show`
- Improved check for write permissions when installing
- Plus assorted bugfixes and improvements
Overview of changes in GLib 2.54.3
==================================
* Bugs fixed:
691436 glib-mkenums output arch dependent
761102 Increase performance for main loop
776147 gio/glocalfilemonitor.c doesn't handle case G_FILE_MONITOR_EVENT_MOVE...
779182 xdg-open fails with gio open for some uris
782057 Unit tests fail in run-assert-msg-test.sh
785113 glib-mkenums Python port fixes
788990 Include licensing information in output from glib-mkenums, glib-genma...
789637 glib-mkenums: Fails when --ouput file does not exist
789894 Text tool has color from previous line, when overwriting existing text
790030 GResource/GVariant fails to load from non-pointer aligned memory
790093 gio-tool: fix inverted logic in monitor tool
790126 gengiotypefuncs.py is missing from tarballs
790829 glib-genmarshal --body must not generate alias implementations
790934 gtester doesn't handle skipped tests
791235 Fix gschema.dtd regarding flags.
791267 Make gschema.dtd usable.
791296 gtester-report: fix range usage when running as python3 app
791325 Gio handling of thumbnail:: attribute namespace causes inconsistent b...
791334 gbinding.c:898: The target object of type GNetworkAddress has no prop...
791337 Crash opening URIs with g_desktop_app_info_launch_uris_with_spawn()
791720 Criticals in gio/xdp-dbus.h leading to crash under flatpak
791744 gmenumodel test sometimes fails: assertion failed (items_changed_coun...
791754 gdbus-peer test intermittently fails: assertion 'source->ref_count > ...
791906 GSocketListenerClass.event has wrong signature
* Translation updates:
Norwegian bokmål
Version 1.1.0 (2017/11/27)
--------------------------
- Fixed entries sorting when generating mo file (Fixes#78)
- Fixed find method (Fixes#84)
- Refactored POEntry.__cmp__ method (this should fix issues #60, #65 and #79)
- Fixed duplicated entries when merging po file with pot file (fixes#68)
- Fixed "None" string being outputted when polib deals with syntax error in string (Fixes issue #66)
- Added a fuzzy property to entries (Fixes#76)
- Take into account the message context when comparing entries
- Leave occurence untouched if line number is not a number (fixes#80 and #90)
- Fixed test for mo files that was failing because since gettext version 0.19.8.1, msgfmt skips the "POT-Creation-Date" metadata entry (Fixes#86)
- Fixed major revision number comparison
- Dropped python 2.4 support
New in 2.12:
* Added support for catching stack overflow on Hurd/i386.
* Added support for catching stack overflow on Haiku.
* Corrected distinction between stack overflow and other fault on AIX.
* Reliability improvements on Linux, FreeBSD, NetBSD.
* NOTE: Support for Cygwin and native Windows is currently not up-to-date.
NEW IN WAF 2.0.4
----------------
* Enable more advanced warnings of ant_glob on build folders in verbose mode
* Defer node.ant_glob(..., generator=True) evaluation
* Enable 'waf clean' to get the list of files to remove from bld.clean_files
* Define the environment variable WAF_NO_PREFORK to skip pre-forking
* Fix Can't pickle local object '_createenviron.<locals>.encode' exceptions (Python 3.6)
* Improve the Erlang module #2095
* Add task target to parallel_debug outputs #2091
NEW IN WAF 2.0.3
----------------
* Enable install_path=None for Python targets #2087
* Skip empty or duplicates in java user classpath #2084
* Change the unit test summary color scheme to use green and red colors
* Improve the deadlock error message
* Report sys.path values from Context.load_tool to improve error messages
* Cache qrc uic->h conversions to enable qrc re-use across targets
* Output long-running tasks outputs immediately using bld(rule=..., stdout=None)
4.1.0
New itertools:
- split_at
- circular_shifts
- make_decorator - see the blog post Yo, I heard you like decorators for a tour
- always_reversible
- nth_combination (from the Python 3.7 docs)
Improvements to existing itertools:
- seekable now has an elements method to return cached items.
- The performance tradeoffs between roundrobin and interleave_longest are now documented
Upstream changes:
1.30 2018-01-26T15:32:00
- Explicitly escape { and } in a regexp because unescaped { issues a warning now and will become
a fatal error in Perl V 5.32.
- Adopt new repo structure. See
http://savage.net.au/Ron/html/My.Workflow.for.Building.Distros.html.
