The point is that you should be using 1.1.4, the latest release in the 1.1
line, and not 1.1.
Jacob
On Sun, Dec 16, 2012 at 12:38 PM, donarb wrote:
>
>
> On Saturday, December 15, 2012 3:54:10 AM UTC-8, Florian Apolloner wrote:
>>
>> I am strongly against showing
On Sunday, December 16, 2012 12:39:13 AM UTC-8, Michael Anckaert wrote:
>
> Hello everyone
>
> I've tried getting my question answered by the folks over django-users but
> when searching the archives I didn't feel that I would get a sufficient
> response there.
>
This list is not the place
Hello,
Since all major browsers now support SVG [1], I've replaced two images in the
docs with SVG versions [2] [3]. This isn't a new idea [4].
[1] http://caniuse.com/#feat=svg
[2]
https://docs.djangoproject.com/en/dev/topics/http/middleware/#hooks-and-application-order
[3]
Since this isn't really appropriate for django-dev, could we move any
further discussion on this over to the django-users group, please?
Many thanks!
Tom
On Sunday, 16 December 2012 18:53:43 UTC, Zach Borboa wrote:
>
> > 1) Being able to create redirects (which seems to already be on the
>
> 1) Being able to create redirects (which seems to already be on the
> todo-list)
Creating temporary 302 redirects are currently possibly right now. The
TODO is for being able to specify both 301 and 302 redirects through
the admin.
> 2) Being able to specify extra kwargs to pass to a view so
On Saturday, December 15, 2012 3:54:10 AM UTC-8, Florian Apolloner wrote:
>
> I am strongly against showing non-supported versions on PYPI, I also don't
> see why you'd need 1.1 for CI tests if you don't use it (an nobody should)
>
I disagree. I have a client who is currently running a site
Hello everyone
I've tried getting my question answered by the folks over django-users but
when searching the archives I didn't feel that I would get a sufficient
response there.
On my current project I need a mix of builtin Django authentication and
oAuth2 sources. But when writing a custom
Yeah, I agree, as it is, I can't see any reason why I would use it, but I
could see it being useful with some modifications such as:
1) Being able to create redirects (which seems to already be on the
todo-list)
2) Being able to specify extra kwargs to pass to a view so that it would be
On 13 joulu, 22:11, Emil Stenström wrote:
> I just thinking out loud here but: what if another thread does something to
> the previously loaded object? I'm not sure if Django has concurrency tests
> build into the test suite, but if it hasn't it could explain why the code
> is