Hello Everyone.
Please help me. How do I start for gsoc 2020, though I have a good
background in Python and Django as a freelancer.
Thank you.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe
Week ending January 12, 2020.
*Triaged:*
https://code.djangoproject.com/ticket/31140 - Caching of dict containing
SafeText objects fails with bmemcached. (invalid)
https://code.djangoproject.com/ticket/31141 - translation.E004 shouldn't be
raised on sublanguages when a base language is available
Hi.
I created a Wiki page for GSoC 2020
https://code.djangoproject.com/wiki/SummerOfCode2020
Check it out. Read over the Project Ideas and the notes for students.
Then I suggest getting involved — now's a great time. :)
Kind Regards,
Carlton
On Monday, 13 January 2020 13:56:13 UTC+1, Priyan
Hi Priyanshu,
I'm a fellow GSoC aspirer. What helped me a lot is checking out the
contributing guide posted on the Django website.
Here is the link:
https://docs.djangoproject.com/en/dev/internals/contributing/
It'll make things a lot easier for you if you've never used Git before and
never trac
Hiya,
The title says it all. It would be dead useful if you could always use
fields rather than the string name of a field, for example in a QuerySet
order_by(), or in the BaseModelAdmin.ordering class attribute (and probably
many more locations).
This has the huge advantage of avoiding string
Hi Everyone,
In Django 3.0 we have Asynchronous support
But where and how to have any benefit from it at this point ?
(as according to docs views/middlewares/ORM does not support it)
do you have any practical/useful example where async can benefit now ?
~Vitaliy
--
You received this message
Hi!
I think you've found the wrong mailing list for this post. This mailing
list is for the development of Django itself, not for support using Django.
This means the discussions of bugs and features in Django itself, rather
than in your code using it. People on this list are unlikely to answer yo
If I understand correctly, currently this works:
Question.objects.order_by(Question.pub_date.field_name)
but your proposal is to avoid the need for ".field_name". I don't think I'd
use that syntax as its more verbose and less readable (to me, anyway).
Having more than one way to write things (s
Eh, sorry if I misunderstand - but adding a "default = true" line to an
AppConfig is the same as addign default_app_config = "foo.apps.FooConfig".
A few things that came to my mind when reading the code:
* You check if there is only one AppConfig available
(https://github.com/django/django/pull/1
Oh, sorry, I just saw that this is discussed (andanswered) in the PR.
Am 13.01.20 um 23:03 schrieb Christian González:
>
> Eh, sorry if I misunderstand - but adding a "default = true" line to
> an AppConfig is the same as addign default_app_config =
> "foo.apps.FooConfig".
>
> A few things that ca
10 matches
Mail list logo
