Update of issue (Trac) rejected (SPAM ...)

[guettli]

I wanted to update this issue https://code.djangoproject.com/ticket/27936

it was not possible. Trac told me this was Spam with this message:

SpamBayes determined spam probability of 98.09%

What can I do now?

I wanted to add this text:

{{{
I still think a visual help like the diagram I painted here 21 month ago 
would be nice.

But maybe I am getting old, wise or just even more lazy.

I think this issue is great for a new comer.

Is "easy picking" applicable for this issue?
}}}

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/30c47e37-cd23-4459-9ce5-0450bee77bb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Easiest front end JavaScript framework to integrate with a Django backend?

[Thanh Tuyền Huỳnh]

Hi guys,

You could refer Vuejs.

Vào 03:20 T.4, 28 Th11 2018 Simon Connah  đã viết:

> I'm in the process of building a website in Django and need to make a
> specific part of my application dynamic. Because of that I'd like to use
> a JavaScript frontend framework to build this portion of the site.
>
> I was wondering if anyone had any recommendations for which JavaScript
> framework I should use that integrates well with a Django backend?
>
> If anyone is curious I am working on an auction style website.
>
> Thank you for any help.
>
> --
> 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, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/ee666748-f8c9-37c9-5c12-491ef61ab70d%40gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CADUa9Eb1vjJ5W61O5ghn8euR3%3D-FU0gWt%2B3D5vdfQadEPpAr1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Easiest front end JavaScript framework to integrate with a Django backend?

[Joel Mathew]

Please provide more useful information that merely suggesting the name of a
framework. Please say why you feel this framework is better for working
with django.
Sincerely yours,

 Joel G Mathew



On Wed, 28 Nov 2018 at 18:36, Thanh Tuyền Huỳnh <
huynhthanhtuyen...@gmail.com> wrote:

> Hi guys,
>
> You could refer Vuejs.
>
> Vào 03:20 T.4, 28 Th11 2018 Simon Connah  đã viết:
>
>> I'm in the process of building a website in Django and need to make a
>> specific part of my application dynamic. Because of that I'd like to use
>> a JavaScript frontend framework to build this portion of the site.
>>
>> I was wondering if anyone had any recommendations for which JavaScript
>> framework I should use that integrates well with a Django backend?
>>
>> If anyone is curious I am working on an auction style website.
>>
>> Thank you for any help.
>>
>> --
>> 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, send email to django-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/ee666748-f8c9-37c9-5c12-491ef61ab70d%40gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CADUa9Eb1vjJ5W61O5ghn8euR3%3D-FU0gWt%2B3D5vdfQadEPpAr1w%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAA%3Diw__eLGX9J5bD_eZCBG8pHa9bRXXYtfPPe8wYr77Q0L7AXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forbidden (CSRF token missing or incorrect.)

[Rabah Saadi]

Any Clue guys ??, Please

Le mercredi 21 novembre 2018 05:38:19 UTC-8, Rabah Saadi a écrit :
>
> Hello,
>
> I've been using Django 2.2Dev for a while now, since April 2018, and it is 
> working just fine (I got my reasons why Django Dev). But since the last git 
> pull, it shows the CSRF token missing, on every page has a form with CSRF 
> token. 
>
> Is there something broke or ... ? since My Django-2.2Dev before the last 
> "git pull" was working just fine.
>
> PS : Donwgrade to Django 2.1.3 stable, works fine too.
>
> thank you.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/e2e990f8-b624-4fe0-b57b-dd812eba166a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Easiest front end JavaScript framework to integrate with a Django backend?

[Jason]

Its really personal preference at times, especially for personal projects.  
That said, when it comes to frameworks like angular, react, vue, picking 
one is like picking a version control solution.  

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c3112a43-a617-492d-b79c-2223ea3b201b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: why created_at is greater than updated_at while inserting data in table

[Nelson Varela]

I think it has to do with django adding timezone.now() on each field with 
auto_now on it when saving to the databse.. the code for the first field 
will get timezone.now() slightly earlier then the second one 

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c3ab68d5-386b-46a9-a7b3-bcb033e2ad3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Easiest front end JavaScript framework to integrate with a Django backend?

[Joel Mathew]

I've been thinking a lot about the most painless way of learning a
javascript framework. My project is almost complete, and so far everything
has been written in javascript using jquery. But for what I have planned
next, a framework would be immensely helpful. I just wish it was as easy as
learning python and django!
Sincerely yours,

 Joel G Mathew



On Wed, 28 Nov 2018 at 19:37, Jason  wrote:

> Its really personal preference at times, especially for personal
> projects.  That said, when it comes to frameworks like angular, react, vue,
> picking one is like picking a version control solution.
>
> --
> 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, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/c3112a43-a617-492d-b79c-2223ea3b201b%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAA%3Diw_86fyGaehzSn1s3uqAmv%2BqkNuo5nqewN9yGZXRr1Ui5YQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Update of issue (Trac) rejected (SPAM ...)

[Tim Graham]

I marked your comment as "ham" so maybe it'll pass the Bayes filter now. 
"Easy pickings" is subjective but I wouldn't consider that issue "easy" 
since there's not a clear consensus about how to proceed.

On Wednesday, November 28, 2018 at 5:10:06 AM UTC-5, guettli wrote:
>
> I wanted to update this issue https://code.djangoproject.com/ticket/27936
>
> it was not possible. Trac told me this was Spam with this message:
>
> SpamBayes determined spam probability of 98.09%
>
> What can I do now?
>
> I wanted to add this text:
>
> {{{
> I still think a visual help like the diagram I painted here 21 month ago 
> would be nice.
>
> But maybe I am getting old, wise or just even more lazy.
>
> I think this issue is great for a new comer.
>
> Is "easy picking" applicable for this issue?
> }}}
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8ef6c577-14ac-491a-a511-8c6ce1a03c35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: why created_at is greater than updated_at while inserting data in table

[Ankit Khandewal]

is there any fix to this?

On Wednesday, 28 November 2018 12:43:03 UTC+5:30, Ankit Khandewal wrote:
>
> hello, i am using this code to update created_at and updated_at in models:
> created_at = models.DateTimeField(auto_now_add=True)
> updated_at= models.DateTimeField(auto_now=True,null=True)
>
> but however there is created _at is greater than updated_at when data is 
> inserted: 
>
>created_at  -> 2018-11-26 11:11:30.020989
>updated_at -> 2018-11-26 11:11:30.019762
>
> please help, thank you.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/dd230d20-c51d-4497-b46d-d692086b1bdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Easiest front end JavaScript framework to integrate with a Django backend?

[Andréas Kühne]

The problem is it isn't easy to recommend a javascript framework because
there are so many and all have different pros and cons. Another thing is
that they are also very subjective in what you need / want. Django itself
isn't biased towards one or the other. Also communicating with django
itself would however be simplified if you use Django Rest Framework
alongside the current solution you have.

So recommending one isn't as easy as saying how to use a template in django
itself :-)

Regards,

Andréas


Den ons 28 nov. 2018 kl 15:29 skrev Joel Mathew :

> I've been thinking a lot about the most painless way of learning a
> javascript framework. My project is almost complete, and so far everything
> has been written in javascript using jquery. But for what I have planned
> next, a framework would be immensely helpful. I just wish it was as easy as
> learning python and django!
> Sincerely yours,
>
>  Joel G Mathew
>
>
>
> On Wed, 28 Nov 2018 at 19:37, Jason  wrote:
>
>> Its really personal preference at times, especially for personal
>> projects.  That said, when it comes to frameworks like angular, react, vue,
>> picking one is like picking a version control solution.
>>
>> --
>> 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, send email to django-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/c3112a43-a617-492d-b79c-2223ea3b201b%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAA%3Diw_86fyGaehzSn1s3uqAmv%2BqkNuo5nqewN9yGZXRr1Ui5YQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAK4qSCdrSMOKjcmNvKWYW05NB4-ZEbJu78QiOFvnz%2BJ%3D2bdkuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: why created_at is greater than updated_at while inserting data in table

[Ankit Khandewal]

and with this method created_at and updated_at both arguments will trigger 
the field update event with timezon.now(), is there any other method to 
enter only created_at at time of inserting 

On Wednesday, 28 November 2018 12:43:03 UTC+5:30, Ankit Khandewal wrote:
>
> hello, i am using this code to update created_at and updated_at in models:
> created_at = models.DateTimeField(auto_now_add=True)
> updated_at= models.DateTimeField(auto_now=True,null=True)
>
> but however there is created _at is greater than updated_at when data is 
> inserted: 
>
>created_at  -> 2018-11-26 11:11:30.020989
>updated_at -> 2018-11-26 11:11:30.019762
>
> please help, thank you.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/7f97cc2d-45b4-488b-a709-d9c2fb313d08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.