<commit_before>================================ Next release ================================

Features:
    - ZooKeeper: A ZooKeeper-contrib is now available, for interacting
      with ZooKeeper ensembles. In addition to a ZooKeeper-client
      provider, a few processors were added as well.

    - AMQP: Support for providing AMQP-connections, consuming messages
      and processing them in pipelines, as well as a simple helper
      for creating and providing AMQP-based RPC-clients.

    - Built-in and contrib providers now use "processor: ..." instead
        of "pipeline: ...", and are able to depend on arbitrary dependencies.
        The dependencies are invoked with the baton as the first and
        only argument.

        This makes it easier for one provider to call a function on another
        provider.

New processors:
    - get-zookeeper-children: Get a list of children for a ZooKeeper node.
    - get-zookeeper-data: Get the data of a ZooKeeper node.
    - zookeeper-node-exists: Check whether a given ZooKeeper node exists.
    - set-zookeeper-data: Set the contents of a ZooKeeper node.
    - create-zookeeper-node: Create a ZooKeeper node.

Internal changes:
    - piped.processing now uses stores the processor name under the
        '__processor__' key instead of 'processor', enabling processors to
        take 'processor' as a keyword argument.

Backward-incompatible changes:
    - The syntax for creating processors in the YAML configuration has changed.
        Using "processor: processor_name" is no longer supported. Use

            - processor_name

            OR

            - processor_name:
                foo: bar

            OR

            - __processor__: processor_name
              foo: bar

         instead.

Bug fixes:
    - #21: When tracing, if a processor asynchronously raised an exception,
      the trace token could be lost, causing the trace to be incomplete.

    - #18: Twisted 11.1 changed some default behaviour, causing debug-mode
       and tracing to break.

========================== Release 0.2.0 2011-10-17 ==========================

Features:
    - Tracing: Processing in pipelines can now be traced. See the tracing
        tutorial.

    - web_provider: The web resources now support an additional setting in<commit_msg>updated CHANGES.txt with the web_processor/provider changes<commit_after>================================ Next release ================================

Features:
    - ZooKeeper: A ZooKeeper-contrib is now available, for interacting
      with ZooKeeper ensembles. In addition to a ZooKeeper-client
      provider, a few processors were added as well.

    - AMQP: Support for providing AMQP-connections, consuming messages
      and processing them in pipelines, as well as a simple helper
      for creating and providing AMQP-based RPC-clients.

    - Built-in and contrib providers now use "processor: ..." instead
        of "pipeline: ...", and are able to depend on arbitrary dependencies.
        The dependencies are invoked with the baton as the first and
        only argument.

        This makes it easier for one provider to call a function on another
        provider.

New processors:
    - get-zookeeper-children: Get a list of children for a ZooKeeper node.
    - get-zookeeper-data: Get the data of a ZooKeeper node.
    - zookeeper-node-exists: Check whether a given ZooKeeper node exists.
    - set-zookeeper-data: Set the contents of a ZooKeeper node.
    - create-zookeeper-node: Create a ZooKeeper node.
    - web-client-get-page: Getting a web page.

Internal changes:
    - piped.processing now uses stores the processor name under the
        '__processor__' key instead of 'processor', enabling processors to
        take 'processor' as a keyword argument.
    - DummyRequest moved back from web_provider to test_web_provider as it uses
        code from the twisted test suite, which shouldn't be used in production.

Backward-incompatible changes:
    - The syntax for creating processors in the YAML configuration has changed.
        Using "processor: processor_name" is no longer supported. Use

            - processor_name

            OR

            - processor_name:
                foo: bar

            OR

            - __processor__: processor_name
              foo: bar

         instead.
    - The processors proxy-forward and chain-web-requests were removed because
        they used code from the twisted test suite, which shouldn't be used in
        production. They might come back at a later time, but no time-frame can
        be given at this moment.

Bug fixes:
    - #21: When tracing, if a processor asynchronously raised an exception,
      the trace token could be lost, causing the trace to be incomplete.

    - #18: Twisted 11.1 changed some default behaviour, causing debug-mode
       and tracing to break.

    - #19: DummyRequest are now only used in the tests, in order to avoid using
        code from the twisted test suite in production.

========================== Release 0.2.0 2011-10-17 ==========================

Features:
    - Tracing: Processing in pipelines can now be traced. See the tracing
        tutorial.

    - web_provider: The web resources now support an additional setting in
{'fraction_non_alphanumeric': 0.0935483870967742, 'fraction_numerical': 0.007210626185958254, 'mean_word_length': 2.6937631394533987, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7093789', 'n_tokens_mistral': 1399, 'n_tokens_neox': 1255, 'n_words': 608}