tkdchen

Please support Django 1.11.x and 2.0.x

4

I'm a Nitrate maintainer which uses this cool package to serialize data. It has been migrated to work with Django 1.11.x and 2.0.x will be the next version to work...

Why is lxml restricted to specific versions?

3

lxml is restricted to `

Migrate to django-environ

11

This patch uses django-environ and drop deprecated and old packages django-cache-url, dj-email-url, dj-database-url and dj-cache-url. Tests are updated according to the behavior of django-environ. Signed-off-by: Chenxiong Qi

/report/testing/?r_product=1&r_created_since=&r_created_before=&report_type=per_build_report

Add mypy check to testenv and CI

2

As per subject. AC: * Add mypy to tox.ini * Run the mypy check in GH CI. * Fix any issues detected.

Run Nitrate within virtual environment inside container

1

No RPM is required to be installed. This issue will cause a little big change to the Containerfile. Both `Containerfile` and `Containerfile-worker` are affected. AC: * Update Containerfile and Containerfile-worker...

AC: * Pin dependencies in install_requires and extras * Compile requirements.txt from pinned dependencies

Drop RPM package build completely

1

Major reason and consideration: - reduce the effort to maintain the builds - easy to pin the dependencies - make it clear to install and distribute via container images AC:...

`Nitrate.Utils.formSerialize` is used to convert form element values into JavaScript object, and send it in AJAX request. This issue aims to investigate how the `formSerialize` is used among the features...