Microsoft probably will take Django support to the next level with Windows
Subsystem for Linux. It's still beta but a very promising one. Not only it
should make compiling Python module binaries (like lxml) much easier, it
also fixes binary / nix specific support of node.js / Ruby packages.
On
CSS variables are long time available at server-side via LESS / SASS
compilers. For example MediaWiki has built-in ResourceLoader that includes
LESS compiler and JS minifier. It uses caching to re-compile only when
source .less or .js are changed. Everything works even with IE8. But
MediaWiki i
Hi everyone!
I got curious to the current state of this work so I thought I save
everyone some work and give you a bunch of links:
- Main PR where the work is being done:
https://github.com/django/django/pull/7482 - Seems there are conflicts
with master that needs to be resolved.
-
On Saturday 29 April 2017 03:50:16 Tim Graham wrote:
> I would expect test data population to happen using migrations rather than
> in the test runner. Can you elaborate on your use case and say if that
> method would be unsuitable?
>
Apparently, many people think that migrations are the wrong to
Avoiding migrations, one can populate test data with a post_migrate signal
handler. django.contrib.contenttypes already does this to fill the DB with
content types, see
https://github.com/django/django/blob/c651331b34b7c3841c126959e6e52879bc6f0834/django/contrib/contenttypes/apps.py#L18
. To do it
I believe I was not clear.
I do use migrations to populate Enums and other data that should also be
available in production.
The code I am sending is to load fixtures on the database.
This way all tests can assume the same set of data and we all the fixtures
are loaded in one place, which in m
>
> Actually, if I may ask, how else would one load bunches of fixtures in the
> DB and run tests in parallel without my PR ?
>
As I said, register a post_migrate handler during testing that loads your
data. It will run during the creation of the first database in
connection.creation.create_test_d
Triaged
---
https://code.djangoproject.com/ticket/28121 - force_text incorrectly
handles SafeBytes under PY3 (wontfix)
https://code.djangoproject.com/ticket/28131 - Template variable "perms"
single-attribute lookup does not work as documented (accepted)
https://code.djangoproject.com/ti
