On Mon, Mar 13, 2017 at 12:58 PM, Etienne Robillard wrote:
>
> As far I know Django channels is a Django framework enforcing a specific
> messaging protocol in mind.
Honnestly I thought the messaging protocol was just msgpack.
> I don't see how implementing ASGI could help to build more scalabl
I think people are always going to run into such kind of issues until they
decide to add django-master to their test matrix, so that each dependency
and project should always have the chance to be ready for the next version
of Django "0day". But perhaps I'm missing something.
Best
James
--
You
Hi all!
Life with DJANGO_SETTINGS_MODULE has been great. However, it requires the
settings to be an importable module. In most cases, this is a straight
forward "simple" python script.
Sometimes it looks like it could make sense to add an environment variable
that could use a file that is not imp
There are indeed a nice handful of apps out there that help doing this
in different manners. While we're at it, my own way is to make every
project a python package with a setup.py. So the settings can always
be imported. Then I let docker swarm or kubernetes handle environment
variables which are
Without diving into implementation details, I recon I've been taught the
same as Shai. An exception type should have only one purpose, thus testing
the type /should/ be sufficient imho. That said, if you want to TDD the
message, you're going to code a test for it, is there really another way ?
;)
Le 7 avr. 2017 10:43 PM, "James Bennett" a écrit :
> On Thu, Apr 6, 2017 at 5:22 PM, James Pic wrote:
>
>> Do I need this to deploy my projects ? No of course, because I use the
>> prettiest way hhihihi ;) I'm more than happy to win a debate
>>
>
> Ple
Tobias, Adam, I have "imagined" you this dialogue where you're helping
people deploy an open source citizen lobbying tool in Django in an NGO was
not to make you look bad of course, the intention was rather the inverse of
that. This situation, and exact dialogue, I have actually had, see the
source
tl;dr
I'm not debating deployment here: my automated deployments are fine
the way it is today: I love linux and env vars, shells and subshells
and so on.
I'm /reporting/ that users have been fighting the lack for
DJANGO_SETTINGS_FILE for as long as I can remember.
In many case, they loose the fi
Thanks friends, of course Daniele for the backup, and also James for
the advice of course now that my first emotional reaction is over -
thanks for your tolerance.
Thanks for reading pretty much everything I have on this subject,
looking forward to read feedback from all django-dev contributors of
101 - 109 of 109 matches
Mail list logo