Re: moving the class-based View base class out of django.views.generic?

[Paulo Gabriel Poiati]

Very handy +1.
--
[]'s
Paulo Poiati

blog.paulopoiati.com

On Tue, Sep 22, 2015 at 9:09 PM Russell Keith-Magee 
wrote:

> On Wed, Sep 23, 2015 at 7:06 AM, Josh Smeaton 
> wrote:
> >> Could we have permanent backward-compatible (no deprecation timeline)
> >> shims? I'm -0 if not because it's yet-another thing that everyone needs
> to
> >> change when upgrading.
> >>
> > +1
>
> That would be my preferred approach, too.
>
> Yours,
> Russ Magee %-)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers  (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAJxq84_c0qKttEXxqxCKq4iD210JSSaCshQtq_0G7BkD%2BYxD2w%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 developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CABqSV%3DJs1rL%2BZPK0nnb55HQ4DzoPsJ4F%3Du_%3DUvJRfpz2v5eb5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: moving the class-based View base class out of django.views.generic?

[Russell Keith-Magee]

On Wed, Sep 23, 2015 at 7:06 AM, Josh Smeaton  wrote:
>> Could we have permanent backward-compatible (no deprecation timeline)
>> shims? I'm -0 if not because it's yet-another thing that everyone needs to
>> change when upgrading.
>>
> +1

That would be my preferred approach, too.

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAJxq84_c0qKttEXxqxCKq4iD210JSSaCshQtq_0G7BkD%2BYxD2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: moving the class-based View base class out of django.views.generic?

[Josh Smeaton]

>
> Could we have permanent backward-compatible (no deprecation timeline) 
> shims? I'm -0 if not because it's yet-another thing that everyone needs to 
> change when upgrading.
>
> +1 

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/d5d22b50-c8c8-4c64-ac2b-a4603e7dbbed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: moving the class-based View base class out of django.views.generic?

[Collin Anderson]

Could we have permanent backward-compatible (no deprecation timeline)
shims? I'm -0 if not because it's yet-another thing that everyone needs to
change when upgrading.

On Tue, Sep 22, 2015 at 11:23 AM, Marc Tamlyn  wrote:

> The idea has been discussed before and was rejected as needless code churn
> if I remember correctly. I'm afraid I can't remember when or where this
> discussion happened, it could have been an in person one at a sprint, I
> can't immediately find a record on this mailing list. Perhaps the fact it's
> come up again makes it more significant (and we can always keep the import
> shim).
>
> FWIW, I am +0, I can see the reasoning but in my opinion we have worse
> import paths (conf.urls and core.urlresolvers anyone?)
>
>
>
> On 22 September 2015 at 15:58, Tom Christie 
> wrote:
>
>> Yup, I think that's a good proposal.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at http://groups.google.com/group/django-developers.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/61cbcc8c-08d9-42af-83d5-4a8ee3d79dac%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 developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAMwjO1ERvJxM1Zj%3DpOJRTX4zY3dqWg_PBYQ-5vQCPCuP-9i8iw%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 developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAFO84S41FtSqK0qNyLj1iNwc01nUQ%2BQiNps2S1%3Di516AtS5jzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: moving the class-based View base class out of django.views.generic?

[Marc Tamlyn]

The idea has been discussed before and was rejected as needless code churn
if I remember correctly. I'm afraid I can't remember when or where this
discussion happened, it could have been an in person one at a sprint, I
can't immediately find a record on this mailing list. Perhaps the fact it's
come up again makes it more significant (and we can always keep the import
shim).

FWIW, I am +0, I can see the reasoning but in my opinion we have worse
import paths (conf.urls and core.urlresolvers anyone?)



On 22 September 2015 at 15:58, Tom Christie  wrote:

> Yup, I think that's a good proposal.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/61cbcc8c-08d9-42af-83d5-4a8ee3d79dac%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 developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMwjO1ERvJxM1Zj%3DpOJRTX4zY3dqWg_PBYQ-5vQCPCuP-9i8iw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: moving the class-based View base class out of django.views.generic?

[Tom Christie]

Yup, I think that's a good proposal.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/61cbcc8c-08d9-42af-83d5-4a8ee3d79dac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: moving the class-based View base class out of django.views.generic?

[John Paulett]

Definitely seems like a good idea to me.  Even as a frequent CBV user, it
always takes me a few seconds to remember to import from generic.

John Paulett

On Tue, Sep 22, 2015 at 10:41 AM, Tim Graham  wrote:

> Class-based view users, does this proposal from
> https://code.djangoproject.com/ticket/25385 seem like a good one?
>
> ---
>
> Whenever I talk about class-based views and how their concept is separate
> from generic views (typically in a class setting), the question I am asked
> is invariably: if they are different, why do we import View from
> django.views.generic?
>
> To help developers better avoid confusion and better separate the
> concepts, I would like to change the import of the View class. Ideally:
>
> from django.views import View
>
> I would furthermore like to move View from the generic directory into
> it's own module.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/ffad765a-0803-47c1-8bd0-9bd69fff0835%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 developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CANRBGvbcHky7ipVjAV40xJrLZCbUW0UfB8L4agn8rvm4q22CRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

moving the class-based View base class out of django.views.generic?

[Tim Graham]

Class-based view users, does this proposal from 
https://code.djangoproject.com/ticket/25385 seem like a good one?

---

Whenever I talk about class-based views and how their concept is separate 
from generic views (typically in a class setting), the question I am asked 
is invariably: if they are different, why do we import View from 
django.views.generic?

To help developers better avoid confusion and better separate the concepts, 
I would like to change the import of the View class. Ideally:

from django.views import View

I would furthermore like to move View from the generic directory into it's 
own module.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/ffad765a-0803-47c1-8bd0-9bd69fff0835%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.