On Fri, 15 Dec 2017 21:01:39 +
Adam Johnson wrote:
> I would prefer the QuerySet method than documenting parts of Query -
> QuerySet shouldn't have to make guarantees that its interactions with
> Query won't change, plus making Query in some way a public API could
> hamper features. Plus the
Yes, wait until at least 2019 to deprecate those.
https://code.djangoproject.com/ticket/27753
On Mon, Dec 18, 2017 at 10:45 AM, Adam Johnson wrote:
> Please don't do that, as I recall we'll just delete django.utils.six after
> the minimum recommended django version for third party libraries is 2.
Please don't do that, as I recall we'll just delete django.utils.six after
the minimum recommended django version for third party libraries is 2.0.
On 18 December 2017 at 15:05, wrote:
> Hello Asad,
>
> as a first task you can remove the Python2-specifics from
> django/utils/six.py , and depreca
Hello Asad,
as a first task you can remove the Python2-specifics from
django/utils/six.py , and deprecate python_2_unicode_compatible().
Greetings
Дилян
On Wednesday, December 13, 2017 at 3:10:31 AM UTC+1, Asad Ahmed wrote:
>
> Hello everyone,
> I'm new to open source community. I've been wor
Hello everybody,
Currently, we can set extra request/view arguments in a form by overriding
a CBV get_form* method. This way, we can add things such as request.user,
if we also override the Form constructor to accept such arguments.
I'd like to suggest that we add a factory(cls, view) method to t
