Is there any current development involving including websockets in django
core?
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an ema
No, there isn’t.
I assume that “including in core” means at least “making usable in combination
with WSGI and with the ORM”.
Even if we disregard for a minute the fact that WSGI is incompatible with
websockets, the ORM is a hard problem, because current solutions involve either
(a) threads — n
What if we do it with asyncio?
2014-10-28 22:47 GMT+01:00 Aymeric Augustin <
aymeric.augus...@polytechnique.org>:
> No, there isn’t.
>
> I assume that “including in core” means at least “making usable in
> combination with WSGI and with the ORM”.
>
> Even if we disregard for a minute the fact tha
Hi all,
I have created a ticket for this (
https://code.djangoproject.com/ticket/23728) but I would like some input
before I work on it. I will copy the content of the ticket below for ease
of reading:
It would be very useful for continuous deployment, testing, commit hooks,
and other applicat
I'm actually fine with option 1 - always exiting with a status code if no
migrations are found. Since the status code does nothing useful at the
moment, I don't see any backwards compatibility issues, and as long as it's
a suitably small patch, it should be fine.
(As for being surprising compared
