<commit_before>PyAMF Changelog
===============

This file contains information about the changes between the different versions
of PyAMF.

0.4.0 (unreleased)
------------------
 - Flex messaging now uses correct static attributes for encoding. Determining
   static/dynamic attributes on objects is now easier (Ticket:357)
 - Added use_proxy option to amf3 which will automagically convert ObjectProxy
   to dict and ArrayCollection to list on decoding and vice versa on encode.
   Thanks to dthompso for the excellent patch (Ticket: 355)
 - flex.ArrayCollection now subclasses list instead of dict as non-int keys are
   not allowed. IList interface has been implemented. (Ticket:359)
 - Encoding registered subclass of list that define the 'externalised' metadata
   will be encoded as an object. 
 - Encoders how have a 'strict' mode. Not generally useful for the time being
   but will help with developments in the future. Type mapped functions now
   require a second 'encoder' attribute. (Ticket:376)
 - Added support for __slots__. (Ticket:347)
 - ByteArray now does not throw an error when used in the Remoting framework
   (Ticket:379)
 - A new adapter that converts sets.ImmutableSet and sets.Set to tuples before
   encoding. (Ticket:280)
 - A revamped google app engine adapter that checks for the _key attribute in
   an aliased class and first loads the object from the datastore and then
   applies that properties in the object stream. (Ticket:307)
 - New helper function to make it easier to manually add adapters (Ticket:350)
 - Python C-extension for the pyamf.util.BufferedByteStream class. Contributed
   by <NAME> (Ticket:225)
 - New API to add headers such as cookies in pyamf.remoting.client (Ticket:337)
 - Now clearing the context between remoting requests (Ticket:309)
 - Fixed issue with AMF3 class definition references (Ticket:341)
 - More helpful description for register_class args check (Ticket:334)
 - pyamf.register_class now checks to ensure that __init__ args do not have
   any arguments (Ticket:322)
 - Added RemoteObject support for AsyncMessage (Ticket:292)
 - Both Encoders will now raise pyamf.EncodeError if a function is encoded
   (Ticket:311)
 - Twisted Gateway would fall over when returning tuples (Ticket:313)
 - The remoting gateways now send a customizable Server header (Ticket:317)
 - The remoting client now sends a customizable User-Agent header (Ticket:306)
 - Added ability to set the HTTP referer in remoting client (Ticket:316)
 - Fixed issue where the AMF3 encoder assumed objects with a 'tag' attribute
   needed XML encoding. Reported by cy-man (Ticket:303)
 - Solved issue with repr for AbstractMessage. Reported by datafunk (Ticket:283)
 - Content-type was missing in POST requests from the AMF client. Reported by
   magog (Ticket:304)<commit_msg>Updating changelog: fixing incorrect ticket references, adding more bugfixes.<commit_after>PyAMF Changelog
===============

This file contains information about the changes between the different versions
of PyAMF.

0.4.0 (unreleased)
------------------
 - Flex messaging now uses correct static attributes for encoding. Determining
   static/dynamic attributes on objects is now easier (Ticket:357)
 - Added use_proxy option to amf3 which will automagically convert ObjectProxy
   to dict and ArrayCollection to list on decoding, and vice versa on encode.
   Thanks to dthompso for the excellent patch (Ticket:355)
 - flex.ArrayCollection now subclasses list instead of dict as non-int keys are
   not allowed. IList interface has been implemented. (Ticket:349)
 - Encoding registered subclass of list that define the 'externalised' metadata
   will be encoded as an object.
 - Encoders how have a 'strict' mode. Not generally useful for the time being
   but will help with developments in the future. Type mapped functions now
   require a second 'encoder' attribute. (Ticket:378)
-  Added adapter to handle the decimal module and, if strict is set to False,
   silently converts a Decimal instance to a float (Ticket:376)
 - ClassAlias can now be subclassed and three new methods have been added:
   applyAttributes, createInstance, getAttributes all which help to provide fine
   control for object/instance manipulation (Ticket:348)
 - Added support for __slots__. (Ticket:347)
 - Fixed problem when decoding objects that map to GAE db.Model objects with
   required properties (Ticket:342)
 - ByteArray now does not throw an error when used in the Remoting framework
   (Ticket:379)
 - A new adapter that converts sets.ImmutableSet and sets.Set to tuples before
   encoding. (Ticket:280)
 - A revamped google app engine adapter that checks for the _key attribute in
   an aliased class and first loads the object from the datastore and then
   applies that properties in the object stream. (Ticket:307)
 - New helper function to make it easier to manually add adapters (Ticket:350)
 - Python C-extension for the pyamf.util.BufferedByteStream class. Contributed
   by <NAME> (Ticket:225)
 - New API to add headers such as cookies in pyamf.remoting.client (Ticket:337)
 - Now clearing the context between remoting requests (Ticket:309)
 - Fixed issue with AMF3 class definition references (Ticket:341)
 - More helpful description for register_class args check (Ticket:334)
 - pyamf.register_class now checks to ensure that __init__ args do not have
   any arguments (Ticket:322)
 - Added RemoteObject support for AsyncMessage (Ticket:292)
 - pyamf.remoting.ErrorFault.__repr__ now displays the traceback info (if it
   exists). (Ticket:331)
 - Both Encoders will now raise pyamf.EncodeError if a function is encoded
   (Ticket:311)
 - Twisted Gateway would fall over when returning tuples (Ticket:313)
 - The remoting gateways now send a customizable Server header (Ticket:317)
 - The remoting client now sends a customizable User-Agent header (Ticket:306)
 - Added ability to set the HTTP referer in remoting client (Ticket:316)
 - Fixed issue where the AMF3 encoder assumed objects with a 'tag' attribute
   needed XML encoding. Reported by cy-man (Ticket:303)
 - Solved issue with repr for AbstractMessage. Reported by datafunk (Ticket:283)
 - Content-type was missing in POST requests from the AMF client. Reported by
   magog (Ticket:304)
{'fraction_non_alphanumeric': 0.06213065005590161, 'fraction_numerical': 0.026832774317201723, 'mean_word_length': 4.162407254740313, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, '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': '5119958', 'n_tokens_mistral': 1788, 'n_tokens_neox': 1637, 'n_words': 822}