Re: Guessable entry points

`python -m django` as a alias for `django-admin` sounds good. -- Aymeric. > On 30 avr. 2015, at 19:15, Ryan Hiebert wrote: > > https://github.com/django/django/pull/4588 > > > I this PR I suggest to add a `django` entry point that is identical t

Re: Pass exception to error handlers

New ticket created: https://code.djangoproject.com/ticket/24733 Claude -- 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 dj

Re: Guessable entry points

I like the alias. On Fri, May 1, 2015 at 5:58 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > `python -m django` as a alias for `django-admin` sounds good. > > -- > Aymeric. > > > > On 30 avr. 2015, at 19:15, Ryan Hiebert wrote: > > https://github.com/django/django/pull/4588

Re: Guessable entry points

So along this line of thought,  `django-admin` is a good command name?  To me the admin, in the django world is a clear distint concept to what this command does. Besides to be used to it, seems more natural to call it `django`.  Cheers, E. On Fri, May 1, 2015 at 2:33 PM, Michael Ma

Re: Guessable entry points

On Friday, May 1, 2015 at 3:51:50 PM UTC+2, Enrique Paredes wrote: > > So along this line of thought, `django-admin` is a good command name? > Does not really matter imo, that is what we have now and we should not change this without a really good reason. Cheers, Florian -- You received t

Re: Guessable entry points

On 1 mai 2015, at 15:51, Enrique Paredes wrote: > So along this line of thought, `django-admin` is a good command name? Well, it’s a reasonably unambiguous way to refer to the django-admin command, which is good for the docs. “django” is more ambiguous: it can refer to the framework itself (

Re: Guessable entry points

Yes to python -m django No to django as another alias for django-admin. After all, someone who is just "guessing" will probably type dj and get django-admin[.py] anyway. On 1 May 2015 at 15:03, Aymeric Augustin wrote: > On 1 mai 2015, at 15:51, Enrique Paredes wrote: > > > So along this line of

Rename *SSL* settings to *TLS*

After searching through the documentation for a few TLS related settings, I failed to find anything. A while later, I found them as *SSL*. I'd like to suggest renaming settings that mention SSL to TLS, to reflect that the former is now deprecated. eg: SECURE_PROXY_SSL_HEADER -> SECURE_PROXY_TL

Re: Rename *SSL* settings to *TLS*

I don't think it's really worth changing, but if anything, I'd recommend HTTPS rather than TLS, as that doesn't care about the underlying protocol which may change again in the future. Or maybe go with PROXY_SCHEME_HEADER or something. On Friday, May 1, 2015 at 12:23:32 PM UTC-4, Hugo Osvaldo B

Redirect loop detection in test client is incorrect

This is related to the ticket #24713, I'm trying to fix this issue and I was thinking about using a variable to know how much time a single url can be repeated on the redirects. Is two time sufficient or we will have another case that need 3 times. If you agree using a variable is it okay to pass

Re: Redirect loop detection in test client is incorrect

Is there any disadvantage to making it some "large" number like 10? In that case it probably wouldn't need to be configurable. The additional time to do 10 loops instead of 2 is probably trivial (and it's an unexpected condition anyway). On Friday, May 1, 2015 at 1:36:32 PM UTC-4, Mounir Messel

Re: Redirect loop detection in test client is incorrect

I think 10 is already too much, it about redirecting to the same page N times. Page1 to Page, Page2 to Page3 and Page3 to the Page1: N=2 redirects to the Page1. Do you think 10 times make senses? In my opinion it's too much and the need to raise an error to make developers know about something w

Re: Allow deferral of ModelSignal callback invocation until after transaction commit

Hi, > On 30 apr 2015, at 18:42, Carl Meyer wrote: > > transaction-hooks is actually fairly small and understandable too. And I > don't think it's hard to use for this situation, either; you'd just need > to use `connection.on_commit` in your signal handler if you wanted to > delay some action un

Re: Redirect loop detection in test client is incorrect

We've already the max total redirects counts it's 20 if len(redirect_chain) > 20: # Such a lengthy chain likely also means a loop, but one with # a growing path, changing view, or changing query argument; # 20 is the value of "network.http.redirection-limit" from Firefox. raise Red

Re: Redirect loop detection in test client is incorrect

My thinking is that a redirect loop of n>2 doesn't seem likely to exit on its own if the developer doesn't intend it to, thus the n we pick shouldn't really matter. On Friday, May 1, 2015 at 2:27:57 PM UTC-4, Mounir Messelmeni wrote: > > We've already the max total redirects counts it's 20 > > i

Re: Redirect loop detection in test client is incorrect

If it helps, I believe Chrome and Firefox have a limit of 20, and Internet Explorer have a limit of 10. On Friday, May 1, 2015 at 2:27:57 PM UTC-4, Mounir Messelmeni wrote: > > We've already the max total redirects counts it's 20 > > if len(redirect_chain) > 20: > # Such a lengthy chain likel

[ANNOUNCE] Django bugfix releases issued: 1.8.1 and 1.7.8

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2015/may/01/bugfix-releases-issued/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group a

Re: Allow deferral of ModelSignal callback invocation until after transaction commit

Hey guys, Thanks for the great feedback and replies. Generally agree with everyone that post-commit hooks shouldn't be strictly coupled to the signals framework philosophically speaking. I disagree with Carl's premise that using `connection.on_commit` in your signal handler is simpler than add

Re: Allow deferral of ModelSignal callback invocation until after transaction commit

Hey guys, Thanks for the great feedback and replies. Generally agree with everyone that post-commit hooks shouldn't be strictly coupled to the signals framework philosophically speaking. I disagree with Carl's premise that using `connection.on_commit` in your signal handler is simpler than add