add prefered/default protocol in the sites framework #26079

[Eric Rouleau]

Hi

I've created a ticket to propose adding a preferred/default protocol in the 
"sites" framework at https://code.djangoproject.com/ticket/26079

tim suggested I bring this to the mailing list and said the following:

I'm not immediately convinced that a database field is the way to go for a 
> couple reasons:
>
>1. It would make data less portable between development (where SSL is 
>often not in use) and production.
>2. I'm not sure it's a common case that only some sites would use SSL 
>but not others.
>
> A third-party library called django-hosts, which djangoproject.com uses, 
> adds a setting called ​HOSTS_SCHEME 
> 
>  to 
> solve this. I think there's been some discussion about merging at least 
> parts of this library into core since it solves common problems.
>
> See also #10944  (we might 
> close this ticket as a duplicate of that one) and #23829 
>  (about customizing 
> ping_google to allow https). I think the best course of action would be 
> to consider this feedback and write to the DevelopersMailingList 
>  with your 
> proposal. Either solution of a new setting or a new database field need 
> feedback from a wider audience. Thanks!
>

   - actually I would say it is even more portable as you 
   would probably use different databases between dev and prod , meaning you 
   can have http in dev but https in prod
   - its not just for SSL but also maybe a it could be used with other 
   protocols/schemes such as dav, webcal, feed
   - third party libraries could now have a definitive way of generating a 
   full URL 

what do you guys think?

-- 
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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/4daa6fb3-071a-4ca0-849c-63283cc3737b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bank of examples.

[Parki]

I've just started out to learn Django and I realize how great would be if 
we had a bank of Django examples.
I would have it, so I want you to contribute.
https://github.com/Parki0/djangoexamples

-- 
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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/7dfb36c8-1865-4192-afc4-4c7853dca741%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

deadlock risk from using cache a load time

[John Bazik]

I'm encountering a nested call to apps.populate in 1.8.7 which causes 
deadlock at load time.  It's called first from django.setup(), then from 
LocMemCache and the process hangs on a lock.  I'm posting here because I 
think the problem is principally within django - the apps I'm using are 
doing reasonable things.

I posted the details to django-users, but the only response I've gotten is 
a suggestion to ask you folks:

https://groups.google.com/forum/#!topic/django-users/WiRzQ8EFOdo

John

-- 
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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/55d39e32-e636-4d47-8a3b-ccac7c68d5ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: deadlock risk from using cache a load time

[Florian Apolloner]

On Wednesday, January 13, 2016 at 6:58:25 PM UTC+1, John Bazik wrote:
>
> I'm posting here because I think the problem is principally within django 
> - the apps I'm using are doing reasonable things.
>

I wouldn't call multisite/hacks.py reasonable :D That said, unpickling 
models requires apps to be populated (relations etc…), therefor do not 
attempt to do such an action during population.

Cheers,
Florian

-- 
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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/477ba36e-26e1-4650-99e9-0723609c6f40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: deadlock risk from using cache a load time

[John Bazik]

> I wouldn't call multisite/hacks.py reasonable :D That said, unpickling 
> models requires apps to be populated (relations etc…), therefor do not 
> attempt to do such an action during population.
>

Thanks.  Shai offered the same opinion and I'm following up with the 
django-cms developers.

John 

-- 
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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1eda3642-48ba-464a-945f-d51fc9427f7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.