> On Sat, May 30, 2015 at 4:19 PM, Florian Apolloner
> wrote:
>> ie how would it use Django's current featureset which is basically
>> blocking
>> everywhere…
>
> On Sat, May 30, 2015 at 4:40 PM, Emil Stenström wrote:
>> The separate process would have none of Django's features, it would just
>>
On Sat, May 30, 2015 at 4:19 PM, Florian Apolloner
wrote:
> ie how would it use Django's current featureset which is basically blocking
> everywhere…
On Sat, May 30, 2015 at 4:40 PM, Emil Stenström wrote:
> The separate process would have none of Django's features, it would just be
> a way to se
Report for week ending May 30, 2015:
Triaged
---
https://code.djangoproject.com/ticket/24850 - Squashed migration not
recognized as an initial migration (duplicate)
https://code.djangoproject.com/ticket/24851 - Regression in reverse
one-to-one field in list_display (accepted)
https://c
They were dropped as part of the removal of the old code that supported
syncing apps without migrations.
https://github.com/django/django/commit/7e8cf74dc74539f40f4cea53c1e8bba82791fcb6
You could probably reimplement them at least to some extent using the new
schema backends. By the way, I susp
Tim,
I've just realised that there is no sql* commands in the newest Django.
Generating SQL from models was very useful. Why do you decided to drop that
functionality? Because of builit-in migrations?
Can you just bring them back?
Thanks.
Marcin.
On Friday, May 29, 2015 at 7:26:26 PM UTC+2,
Hi Reiner.
You'll get answers to questions like this on the django-users email list, <
django-developers@googlegroups.com> - the web interface is <
https://groups.google.com/forum/#!forum/django-users>.
The list you've posted to is django-developers, which is for the discussion
of the development
Hello,
It would be very helpful to create forms in the model only. The thing I miss
is a simple text in the model that would appear in the output form exactly
on the position from the model as text e.g. in a Paragraph.
I fail to do it myself from documentation.
Example :
in models.py
class Exa
Hi,
The separate process would have none of Django's features, it would just be
a way to send messages to connected clients. Here's an example of how it
could work:
- Client A and Client B connects to my site. Django serves the start
page as normal.
- The start page serves up a javasc
Hi Emil,
while supporting server-sent events (or even websockets for that matter)
would be great, this is basically a problem which has to be tackled in WSGI
first in my opinion. That said, when you talk about a separate process, how
would it look like (aside from using asycio), ie how would i
I just wanted to add that this looks GREAT. Maintaining the old colors was
a smart move, as this makes things familiar but still new. This work was
long overdue!
/E
On Saturday, 23 May 2015 14:00:18 UTC+2, elky wrote:
>
> HI Andy,
>
> Yes, this thread is actual for discussing this theme.
>
> Cu
Hi Collin,
I'll answer in this thread to keep here things tidy.
Since Server-Sent Events are just HTTP you can scale them the same way you
scale your normal web app. Split users so some users hit one server and
some users hit another. Then let Django communicate with all server
processes inste
Hi Emil,
I also like "server sent events" (EventSource). They get through proxies
much more reliably than WebSockets. :)
"You would start the process separately, add a script tag to your page, and
all clients that connected to the page would be connected to the process.
Now Django could push m
On Saturday, 30 May 2015 18:51:33 UTC+2, Emil Stenström wrote:
>
> *I will split the specific suggestions into three different e-mail
> threads, so we can discuss them separately*.
>
Here's are the three different proposals:
https://groups.google.com/forum/#!topic/django-developers/fRPXSGnPng0
Hi,
This is the third feature proposal as part of my general drive for
getting Django to work better for javascript heavy sites.
Support Server-Sent Events
--
If you want a snappy user experience, AJAX polling isn't enough. There
are two major ways to get out of the r
Hi,
This is the first feature proposal as part of my general drive for
getting Django to work better for javascript heavy sites.
Template Components
---
React.js popularized the notion that in front-end development, code
organization should be based on interface components, n
Hi,
This is the second feature proposal as part of my general drive for
getting Django to work better for javascript heavy sites.
Support a javascript template language on the server
The multiple template engine work has made it possible to
Hi!
A couple of weeks ago I held a presentation on PyCon Sweden 2015 with
the title "Why Django Sucks". The idea was to follow in the footsteps of
great conference talks like these:
https://www.youtube.com/playlist?list=PLGYrvlVoAdf9j3v_teol3s7hl8gkUd8E2
These talks are great because they enc
>
> An app doesn't necessarily have to use its own patterns. With that said,
> it's up to the user to make sure it works if they are to mess with the
> app_name. Two conflicting apps can be installed with different namespaces,
> but there will always be a default (the last one, if there is no n
18 matches
Mail list logo
