It seems that the issue is somehow related to empty trac_session cookie which
somehow has got set. Here is the curl request which can be used to obtain the
403 response:
curl -I -H 'Cookie: trac_session=' https://code.djangoproject.com/ticket/2659
Clearing the cookies solved the problem, so
Trying to browse any ticket on code.djangoproject.com yields 403 Forbidden,
with a message “TICKET_VIEW privileges are required to perform this operation.
You don't have the required permissions.”. An attempt to login via
https://code.djangoproject.com/login results in 502. It has been broken
Hi,
I’m raising the issues found in ticket #16284 (
https://code.djangoproject.com/ticket/16284 ). To sum up, here is how
Django currently chooses translation in jsi18n:
— It searches for a translation for the active language.
— If the above is not found, it searches for the
W dniu 24.10.2013 18:33, Gavin Wahl pisze:
I really like the idea of implementing this as a url pattern decorator.
This seems similar to Alex Gaynor's talk about everything being a view.
It's more flexible than a middleware because you can decorate any part
of the urls tree, such as the patterns
On 10/09/2013 08:38 PM, Tim Graham wrote:
A drawback is that it will introduce some noise in the commit history in
the short term and make git blame less efficient.
Note however that there is “-w” option for git blame, which does the
following: “Ignore whitespace when comparing the parent’s
There is a SimpleTestCase.settings method added in commit 0dc6420ⁱ,
which, according to the docstring, returns “A context manager that
temporarily sets a setting and reverts back to the original value when
exiting the context.”. In commit a3a53e0² its implementation has been
simplified so that
W dniu 21.05.2013 14:38, Russell Keith-Magee pisze:
These are all reasonable and fairly small I'd be happy to see these
added after the alpha - a ticket and patch would definitely be welcome.
I’ve created a ticket and a pull request with PATCH support for View and
RedirectView (support for
There is a RFC describing HTTP method named PATCH:
http://tools.ietf.org/html/rfc5789
Quoting that RFC:
“ The difference between the PUT and PATCH requests is reflected in the
way the server processes the enclosed entity to modify the resource
identified by the Request-URI. In a PUT
Dnia 2012-12-21, pią o godzinie 11:05 -0800, Anssi Kääriäinen pisze:
> I went with a different approach than the patch for 1.5. At this stage
> as minimal as possible change to get_default_columns() seemed like a
> good idea. See commit a0155f35343afbfd9e98ab9aa4615f06780f697e in
> stable/1.5.x.
>
On 13.12.2012 15:54, Anssi Kääriäinen wrote:
Second, I have created a patch which should allow your work to
continue working in master. See
https://github.com/akaariai/django/commit/94c417d2a29a0f72b26019fc38ef400420097aa4
- the idea is to change get_fields_with_model() so that it doesn't
return
On 29.10.2012 14:34, Krzysztof Jurewicz wrote:
In February, Craig de Stigter released django-typed-models
<https://groups.google.com/d/topic/django-users/63z-ejUQ1Eg/discussion>,
a package implementing inheritance hierarchy for Proxy models with
automatic type recasting. I've written
egards,
Krzysztof Jurewicz
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/aSgkQliZHtYJ.
To post to this group, send email to d
12 matches
Mail list logo
