<commit_before>python-maec
===========

A Python library for parsing, manipulating, and generating MAEC content.

:Source: https://github.com/MAECProject/python-maec
:Documentation: http://maec.readthedocs.org
:Information: http://maec.mitre.org
:Download: https://pypi.python.org/pypi/maec/

|landscape.io badge| |version badge| |downloads badge|

.. TODO: add Travis Badge

.. |landscape.io badge| image:: https://landscape.io/github/MAECProject/python-maec/master/landscape.png
   :target: https://landscape.io/github/MAECProject/python-maec/master
   :alt: Code Health
.. |version badge| image:: https://pypip.in/v/maec/badge.png
   :target: https://pypi.python.org/pypi/maec/
.. |downloads badge| image:: https://pypip.in/d/maec/badge.png
   :target: https://pypi.python.org/pypi/maec/


Overview
--------

A primary goal of the python-maec library is to remain faithful to both the
MAEC standard and to customary Python practices. There are places where these
will conflict, and the goal is to make the library intuitive both to those
familiar with the XML schemas (but less familiar with Python) and also to
experienced Python developers who want to add MAEC support to their programs.

There are currently two levels of APIs for dealing with MAEC content:

- A low-level API is provided by auto-generated XML Schema - Python class
  bindings. These bindings were generated using `generateDS<commit_msg>Include Travis Badge in README.<commit_after>python-maec
===========

A Python library for parsing, manipulating, and generating MAEC content.

:Source: https://github.com/MAECProject/python-maec
:Documentation: http://maec.readthedocs.org
:Information: http://maec.mitre.org
:Download: https://pypi.python.org/pypi/maec/

|travis badge| |landscape.io badge| |version badge| |downloads badge|

.. |travis badge| image:: https://api.travis-ci.org/MAECProject/python-maec.png?branch=master
   :target: https://travis-ci.org/MAECProject/python-maec
   :alt: Build Status
.. |landscape.io badge| image:: https://landscape.io/github/MAECProject/python-maec/master/landscape.png
   :target: https://landscape.io/github/MAECProject/python-maec/master
   :alt: Code Health
.. |version badge| image:: https://pypip.in/v/maec/badge.png
   :target: https://pypi.python.org/pypi/maec/
.. |downloads badge| image:: https://pypip.in/d/maec/badge.png
   :target: https://pypi.python.org/pypi/maec/


Overview
--------

A primary goal of the python-maec library is to remain faithful to both the
MAEC standard and to customary Python practices. There are places where these
will conflict, and the goal is to make the library intuitive both to those
familiar with the XML schemas (but less familiar with Python) and also to
experienced Python developers who want to add MAEC support to their programs.

There are currently two levels of APIs for dealing with MAEC content:

- A low-level API is provided by auto-generated XML Schema - Python class
  bindings. These bindings were generated using `generateDS
{'fraction_non_alphanumeric': 0.11733333333333333, 'fraction_numerical': 0.0, 'mean_word_length': 4.192041522491349, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 18, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 6, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2694652', 'n_tokens_mistral': 954, 'n_tokens_neox': 905, 'n_words': 302}