Well it was my mistake I forgot the '/' in the urls.py of my site where I
included the polls urls. So no bug :)
Am Samstag, 3. März 2018 08:09:01 UTC+1 schrieb Cictani:
>
> Hi,
>
> I'm doing the tutorial right now and I'am at step 3:
> https://docs.djangoproject.com/en/2.0/intro/tutorial03/
>
>
Hi,
I'm doing the tutorial right now and I'am at step 3:
https://docs.djangoproject.com/en/2.0/intro/tutorial03/
I think the path is not correct in the tutorial.
In the tutorial:
path('/', views.detail, name='detail'),
If I do it like that I get a 404 I have to use:
path('//', views.detail,
Two big thumbs up for Ken!
His keen eyes spotted the problem, which was attempting an asynchronous
send from the Celery task. I changed the code to use the synchronous send
and, bingo, the consumer now receives events via the channel layer.
A big thank-you to Ken! And, I'm sure anyone else
In Django 1,8 it worked but in Django 1.11 it throws:
TypeError: context must be a dict rather than RequestContext.
The code is:
class EpilogueNode(template.Node):
def __init__(self): # noqa: D102
self.epilogue_template =
Taking a stab at this - I believe the original problem may be here:
channel_layer.group_send(
settings.CHANNEL_GROUP,
{"type": "epics.message", "text": "Hello World"},
)
Your updateData method is a synchronous method. However,
channel_layer.group_send is an asynchronous
Hi All:
I'm migrating a small application from Django 1.x/Channels 1.x to Django
2.0.2 and Channels 2.0. I've run into an issue whose cause I'm trying to
determine. It could be due to a failure on my part to correctly implement
the channel_layer or it could be due to an
incompatibility with
Well that was my intention to mean that this particular feature (import
statement) seems to lack support for somewhat popular browsers.
Also I think caniuse lags a bit since if I'm not mistaken latest FF
supports import.
And in any case JS errors are not Django related.
2.3.2018 13.30 "Jason"
On Friday, March 2, 2018 at 9:27:29 PM UTC+6, Vinicius Assef wrote:
>
> My bad. It's urls.py
>
> On 2 March 2018 at 12:25, Vinicius Assef
> wrote:
> > Probably you have a problem with route.
> >
> > Check your routes.py again.
> >
> > On 2 March 2018 at 10:28,
My bad. It's urls.py
On 2 March 2018 at 12:25, Vinicius Assef wrote:
> Probably you have a problem with route.
>
> Check your routes.py again.
>
> On 2 March 2018 at 10:28, wrote:
>>
>>
>> On Friday, March 2, 2018 at 6:24:49 PM UTC+6,
Probably you have a problem with route.
Check your routes.py again.
On 2 March 2018 at 10:28, wrote:
>
>
> On Friday, March 2, 2018 at 6:24:49 PM UTC+6, Vinicius Assef wrote:
>>
>> Some time ago I wrote this post [0] about setting Python and Django
>> on
On Friday, March 2, 2018 at 6:24:49 PM UTC+6, Vinicius Assef wrote:
>
> Some time ago I wrote this post [0] about setting Python and Django
> on Dreamhost. They use passenger.
>
> Maybe it's useful to you.
>
>
> [0]
>
On Friday, March 2, 2018 at 9:19:10 AM UTC-3, Tanvir Ahmed wrote:
>
> I am fairly new to the web hosting world. I recently purchased a plan at
> a2hosting. It's a shared hosting plan. After some problems with FastCGI, I
> was told to use passenger to host django. I couldn't find much on this
>
On Friday, March 2, 2018 at 9:19:10 AM UTC-3, Tanvir Ahmed wrote:
>
> I am fairly new to the web hosting world. I recently purchased a plan at
> a2hosting. It's a shared hosting plan. After some problems with FastCGI, I
> was told to use passenger to host django. I couldn't find much on this
>
Some time ago I wrote this post [0] about setting Python and Django
on Dreamhost. They use passenger.
Maybe it's useful to you.
[0]
http://aprenda-python.blogspot.com.br/2016/06/setup-python-with-django-or-pyramid-on-dreamhost.html
On 2 March 2018 at 04:56, Tanvir Ahmed
Hello,
I am fairly new to the web hosting world. I recently purchased a plan at
a2hosting. It's a shared hosting plan. After some problems with FastCGI, I
was told to use passenger to host django. I couldn't find much on this
topic and somehow managed to get the website working. However, soon I
Andrew,
Thanks for taking the time to reply.
In classic fashion, the issue has gone away and I'm not entirely sure why.
I suspect there might have been a page with older code buried somewhere,
trying to do websocket things wrongly, and that was throwing things off.
I'm sure it will rear it's
Jani Tiainen, Your assertion that ES is not very well supported is
incorrect. Most of ES6 is in fact highly supported across browsers except
for certain specifications that are still being worked on regarding
implementation details. For reference, look at
Hi Alberto,
I'm guessing `def blog(request):` is actually `blog_category_posts`, right?
Because you have `` on your URL, our view will receive it as another
parameter, after request. So it should be `def
blog_category_posts(requests, slug):` and then you can get the slug, filter
the posts and
You need to give a proposal detailing what you want to work on. Note that
while you may ultimately improve your skills with the project, your main
goal will be to improve the project.
On 1 March 2018 at 05:25, tola temitope wrote:
> hey, good day guys i am a Django
Thanks @Jani Tiainen, I'll try to do it :)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group,
20 matches
Mail list logo