<commit_before>## Existing Django packages

Package                 Last release  Comment
-------                 ------------  -------
`eav-django`            2014-07-30
`django-mutant`         2016-01-14    Latest real "dynamic models" package
`django-dynamic-model`  (2013-05-09)  Obsolete?
`django-dynamo`         2011-08-03    Obsolete
`vera` (wq)             2016-01-08    Not quite relevant


## Motivation

From `django-dynamo` documentation:

> Dynamic models are beneficial for applications that need data
> structures, which are only known at runtime, but not when the
> application is coded. Or when existing models need to be extended at
> runtime by additional fields. Typical use cases are:
>
> 1. CMS: In content management systems, users often need to maintain
>    content that is unique for their specific website. The required
>    data structures to store and maintain this content is therefore
>    not known to the developers beforehand.
>
> 2. Web Shop: The owner of a web shop has highly customized products,
>    with very special product attributes. The shop developers want
>    the web shop owner to define these attributes herself.
>
> 3. Survey: If you have an application to create and maintain online
>    surveys, you do neither know the questions nor the possible
>    answers at runtime, but let your users define these, as they
>    implement their surveys.



## Requirements
<commit_msg>Notes<commit_after>## Existing Django packages

| Package                 | Last release  | Comment |
| ----------------------- | ------------- | ------- |
| `eav-django`            | 2014-07-30    |         |
| `django-mutant`         | 2016-01-14    | Latest real "dynamic models" package |
| `django-dynamic-model`  | (2013-05-09)  | Obsolete? |
| `django-dynamo`         | 2011-08-03    | Obsolete |
| `vera` (wq)             | 2016-01-08    | Not quite relevant |


## Motivation

From `django-dynamo` documentation:

> Dynamic models are beneficial for applications that need data
> structures, which are only known at runtime, but not when the
> application is coded. Or when existing models need to be extended at
> runtime by additional fields. Typical use cases are:
>
> 1. CMS: In content management systems, users often need to maintain
>    content that is unique for their specific website. The required
>    data structures to store and maintain this content is therefore
>    not known to the developers beforehand.
>
> 2. Web Shop: The owner of a web shop has highly customized products,
>    with very special product attributes. The shop developers want
>    the web shop owner to define these attributes herself.
>
> 3. Survey: If you have an application to create and maintain online
>    surveys, you do neither know the questions nor the possible
>    answers at runtime, but let your users define these, as they
>    implement their surveys.



## Requirements

{'fraction_non_alphanumeric': 0.09103400893163861, 'fraction_numerical': 0.029543112332531776, 'mean_word_length': 2.7429305912596402, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 39, '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': '5051071', 'n_tokens_mistral': 815, 'n_tokens_neox': 738, 'n_words': 356}