Hello community,

here is the log from the commit of package xonsh for openSUSE:Factory checked 
in at 2019-04-05 11:56:53
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/xonsh (Old)
 and      /work/SRC/openSUSE:Factory/.xonsh.new.3908 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "xonsh"

Fri Apr  5 11:56:53 2019 rev:14 rq:687599 version:0.8.11

Changes:
--------
--- /work/SRC/openSUSE:Factory/xonsh/xonsh.changes      2019-02-26 
22:22:13.182070019 +0100
+++ /work/SRC/openSUSE:Factory/.xonsh.new.3908/xonsh.changes    2019-04-05 
11:56:56.546348542 +0200
@@ -1,0 +2,77 @@
+Sat Mar 16 14:21:39 UTC 2019 - Sebastian Wagner <[email protected]>
+
+- update to version 0.8.11
+ - Added:
+  - New ``xonsh.color_tools.short_to_ints()`` function for directly
+    converting a short (0 - 256) color into a 3-tuple of ints
+    represeting its RGB value.
+  - New ``xonsh.ansi_colors.ansi_reverse_style()`` function for
+    converting a mapping of color names to ANSI escape codes into
+    a mapping from escape codes into color names. This is not a
+    round-trippable operation.
+  - New ``xonsh.ansi_colors.ansi_color_escape_code_to_name()`` function
+    for converting an ANSI color escape code into the closest xonsh
+    color name for a given style.
+  - New ``xonsh.events.EventManager.exists()`` method enables the checking
+    of whether events actually exist with out making the event if it
+    doesn't exist.
+  - New command-specific event categories called ``on_pre_spec_run_<cmd-name>``
+    and ``on_post_spec_run_<cmd-name>`` will be fired before and after
+    ``SubpocSpec.run()`` is called.  This allows for command specific
+    events to be executed.  For example, ``on_pre_spec_run_ls`` would
+    be run prior to an invocation of ``ls``.
+  - New ``xonsh.environ.LsColors`` class for managing the ``$LS_COLORS``
+    environment variable. This ensures that the ``ls`` command respects the
+    ``$XONSH_COLOR_STYLE`` setting. An instance of this class is added to the
+    environment when either the ``$LS_COLORS`` class is first accessed or
+    the ``ls`` command is executed.
+  - The ``on_pre_spec_run_ls`` event is initialized with a default handler
+    that ensures that ``$LS_COLORS`` is set in the actual environment prior
+    to running an ``ls`` command.
+  - New ``xonsh.tools.detype()`` function that simply calls an objects own
+    ``detype()`` method in order to detype it.
+  - New ``xonsh.tools.always_none()`` function that simply returns None.
+  - New ``Env.set_ensurer()`` method for setting an ensurer on an environment.
+ - Changed:
+  - The black and white style ``bw`` now uses actual black and white
+    ANSI colore codes for its colors, rather than just empty color
+    sequences.
+  - An environment variable ``detype`` operation no longer needs to be
+    function, but may also be ``None``. If ``None``, this variable is
+    considered not detypeable, and will not be exported to subprocess
+    environments via the ``Env.detype()`` function.
+  - An environment variable ``detype`` function no longer needs to return
+    a string, but may also return ``None``. If ``None`` is returned, this
+    variable is  considered not detypeable, and will not be exported to
+    subprocess environments via the ``Env.detype()`` function.
+  - The ``Env.detype()`` method has been updated to respect the new
+    ``None`` types when detyping.
+  - The ``xonsh.tools.expandvars()`` function has been updated to respect
+    the new ``None`` types when detyping.
+  - The ``xonsh.xonfig.make_xonfig_wizard()`` function has been updated to 
respect
+    the new ``None`` types when detyping.
+  - Event handlers may now be added and discarded during event firing for
+    normal events.  Such modifications will not be applied to until the
+    current firing operation is concluded. Thus you won't see newly added
+    events fired.
+  - xonsh now uses its own vended version of ply. Any installed versions will 
no longer be used. This reflects that ply is no
+    longer distributed as an installable packages.
+  - Updated to used ply version 3.11.
+  - Reverted change in ``give_to_terminal`` to restore working version of
+    ``cmake``, ``rm -i``, etc.  This breaks ``pv | head``.
+ - Deprecated:
+  - The ``xonsh.color_tools.make_pallete()`` function is no
+    longer deprecated, as it is actually needed in other parts of
+    xonsh still, such as ``pyghooks``.
+ - Removed:
+  - All code references to ``$FORMATTER_DICT`` have been removed.
+ - Fixed:
+  - Resolved issues where macro functions were not able to properly
+    accept single-line statements in ``exec`` and ``single`` mode.
+  - Minor fixes to ``xonsh.events.debug_level()``.
+  - Fixed a regression where some interactive commands were not waited for
+    properly for long enough.
+  - Fixed environments not showing in the prompt when using Anaconda Python.
+  - Fixed regression with anaconda activate/deactivate scripts not wokring on 
Windows.
+
+-------------------------------------------------------------------

Old:
----
  xonsh-0.8.10.tar.gz

New:
----
  xonsh-0.8.11.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ xonsh.spec ++++++
--- /var/tmp/diff_new_pack.deHTxQ/_old  2019-04-05 11:56:57.254349046 +0200
+++ /var/tmp/diff_new_pack.deHTxQ/_new  2019-04-05 11:56:57.258349049 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           xonsh
-Version:        0.8.10
+Version:        0.8.11
 Release:        0
 Summary:        A general purpose, Python-ish shell
 License:        BSD-3-Clause AND BSD-2-Clause
@@ -76,7 +76,7 @@
 %{_bindir}/xon.sh
 %doc README.rst logo.txt CHANGELOG.rst
 %doc xontrib
-%doc xonsh/ply/example xonsh/ply/doc/*.html xonsh/ply/ANNOUNCE 
xonsh/ply/README.md xonsh/ply/CHANGES
+%doc xonsh/ply/example xonsh/ply/doc/*.html xonsh/ply/README.md 
xonsh/ply/CHANGES
 %license license
 
 %files -n %{name}-doc

++++++ xonsh-0.8.10.tar.gz -> xonsh-0.8.11.tar.gz ++++++
++++ 2645 lines of diff (skipped)


Reply via email to