In addition, with tools like https://github.com/pyenv/pyenv available that make
changing the currently applicable python version in any given shell extremely
easy, I feel pinning support to a specific operating system version, however
stable, is not the optimal approach
--
You received this m
Week ending January 19, 2019
Triaged
---
https://code.djangoproject.com/ticket/17904 - Custom permissions on proxy
model no longer created (fixed)
https://code.djangoproject.com/ticket/30113 - Ignoring body with
application/json payload causes HTTP 400 (duplicate)
https://code.djangopr
I don't feel like my voice should have much weight, but I think that the
policy as written is better. Debian aims to be stable long term, and for us
to match Debian, especially when not in our LTS releases, seems excessive
to me.
On Mon, Jan 21, 2019 at 9:56 AM Tim Graham wrote:
> When deciding
On Mon, Jan 21, 2019 at 4:34 AM Michael Martinez <
writemichaelmarti...@gmail.com> wrote:
> Hi Andrew
>
> To me, Websockets is the defining use case for using Django Channels. From
> a user POV, saying that Channels is focused on the wrong problem
> (websockets) is like saying Django is too focuse
When deciding when to drop support for Python 2 in Django, there was
consensus to adopt this Python version support policy [0]: "Typically, we
will support a Python version up to and including the first Django LTS
release whose security support ends after security support for that version
of Py
Hi All
Calendar Week 3 -- ending 20 January.
Released Django 2.2a1.
Triaged:
https://code.djangoproject.com/ticket/30089 -- TestClient doesn't
accept data with duplicate keys (SELECT multiple) (Accepted)
https://code.djangoproject.com/ticket/30115 -- inspectdb on SQLite crashes
with TypeE
Alright, thanks for the clarification. I've already asked this question
on Stack Overflow and will now try the same on the django-users mailing
list.
On 20/01/2019 18:39, Adam Johnson wrote:
This mailing list is for the development of Django itself, not for
support using Django. Please use th
Hi Andrew
RE:
> I feel, is that is solves the wrong problem - it's focused on WebSockets,
> which is a niche feature that a few people are happy we provide but most
> people have no practical use for.
>
To me, Websockets is the defining use case for using Django Channels. From
a user POV,
Hi Andrew,
Have you considered Jazzband (https://jazzband.co/) for this ?
Guilhem.
Le jeudi 17 janvier 2019 19:07:06 UTC+1, Andrew Godwin a écrit :
>
> Hi all,
>
> I'm writing to you all to update you on the current situation of Channels
> and related libraries (channels-redis and Daphne) and p
am sorry Noumbissi
you're a very welcome fellow .
On Jan 21 2019, at 9:42 am, Noumbissi Valere wrote:
> Thanks Carlton.
>
> On Mon, Jan 21, 2019 at 9:38 AM Carlton Gibson (mailto:carlton.gib...@gmail.com)> wrote:
> > Hi Folks.
> >
> > First off: can we please keep it civil. Let's offer positive
Thanks Carlton.
On Mon, Jan 21, 2019 at 9:38 AM Carlton Gibson
wrote:
> Hi Folks.
>
> First off: can we please keep it civil. Let's offer positive responses
> where possible. Thanks
>
> There's no harm in people asking for help: there is a contributing guide,
> but if folks aren't finding it, pe
Hi Folks.
First off: can we please keep it civil. Let's offer positive responses
where possible. Thanks
There's no harm in people asking for help: there is a contributing guide,
but if folks aren't finding it, perhaps we need a bigger sign-post.
So...
The place to begin is
here: https://
Hello Noumbissi ,
I think you're skilled in python but you're not enough skilled in "" GOOGLEing"
.
you can start with the officiel django tutorial.
https://docs.djangoproject.com/en/2.1/intro/tutorial01/
Best regards.
On Jan 21 2019, at 1:50 am, noumbissival...@gmail.com wrote:
> Hello Everyone
13 matches
Mail list logo
