Hi Folks,
Have release v1.2.0 for django-yamlconf, a module supporting Django settings via YAML files (searching up the directory hierarchy, e.g., in a K8s environment, adding a "final" set of settings via "/APPLICATION.yaml", see the documentation a https://django-yamlconf.readthedocs.io/en/latest/ for more detailed info.
The updates for the this release are:
- Tagged with ``v1.2.0``.
- Updates to support Django 3.0: Simply use "`six`" instead of the
support "`django.utils.six`" package and use "`render`" instead of
"`render_to_response`".
- `ycsysfiles` should generate executable files if the source template
file is executable.
- Ensure the absolute path is used when searching for YAML control
files. This issue is seen when running Django apps under uWSGI
control.
- Added the built-in attribute ``CPU_COUNT`` (primarily for use in uWSGI
ini files) giving the number of available CPUs.
- Updates to support Django 3.0: Simply use "`six`" instead of the
support "`django.utils.six`" package and use "`render`" instead of
"`render_to_response`".
- `ycsysfiles` should generate executable files if the source template
file is executable.
- Ensure the absolute path is used when searching for YAML control
files. This issue is seen when running Django apps under uWSGI
control.
- Added the built-in attribute ``CPU_COUNT`` (primarily for use in uWSGI
ini files) giving the number of available CPUs.
Take care,
Michael.
--
Michael Rohan
mrohan@acm.org
mrohan@acm.org
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAOCsNFhTf1Ar3paJ-3tJdVVZ1qO%2B-FWEzDOkiDtQwOBHJwiKRw%40mail.gmail.com.
No comments:
Post a Comment