-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2011 07:25 AM, Thibault Jouannic wrote:
> https://github.com/django/django/pull/87
>
> Hope I did everything right.
>
> I've read the submitting patches doc, but is a git pull request
> accepted? Otherwise, Should I upload a patch in the clo
Fwiw, for the last number of months we've been telling people that pull
requests are fine in lieu of uploaded patch, but the pull request still needs
to be linked from a Trac ticket (so Trac remains the single source of truth).
Carl
--
Sent from my Android phone with K-9 Mail. Please excuse my
On Wed, Dec 7, 2011 at 8:25 AM, Thibault Jouannic wrote:
> I've read the submitting patches doc, but is a git pull request
> accepted?
For now, no. We'll be moving to GitHub in the near future, but
currently we're using Subversion/Trac. Upload a patch via the ticket
tracker (code.djangoproject.co
Hi again,
> Please add a patch to the tracker, since it always best if people with the
> problem write it as they know what's missing.
Done.
https://github.com/django/django/pull/87
Hope I did everything right.
I've read the submitting patches doc, but is a git pull request
accepted? Otherwise
Hi,
On Wednesday, December 7, 2011 11:09:38 AM UTC+1, Thibault Jouannic wrote:
>
> If I'm not wrong, only the PUT method can specify POST like
> parameters.
>
Before writing my answer I did look on w3c and at least OPTIONS is allowed
to have a body (can't tell you if it has to be a specific cont
Hi,
> That would be really odd imo and confusing as hell if you find
> PUT/DELETE/HEAD/OPTIONS/whatever data in request.POST
If I'm not wrong, only the PUT method can specify POST like
parameters.
> put_data = QueryDict(self.raw_post_data, encoding=your_encoding)
> not really hard if you ask me.
Hi,
On Wednesday, December 7, 2011 9:33:52 AM UTC+1, Thibault Jouannic wrote:
> So, don't you think the `request.POST` variable should be processed
> for every request with the "x-www-form-urlencoded" content type,
> whatever the http verb is?
>
That would be really odd imo and confusing as hell
Actually, I've been thinking about this issue, read again the bug
report and current thread, and I'd like to re-open the discussion, if
you don't mind.
> request.POST is a
> special-case for a request body submitted with the
> "x-www-form-urlencoded" or "multipart/form-data" content types. This is
Thank you for taking the time to answer.
On 1 déc, 21:41, Carl Meyer wrote:
> However, web browsers do not submit PUT requests from HTML forms (and
> they aren't likely to ever do so, as that proposed HTML5 feature was
> removed [2]).
Yeah, I was aware of that decision. The reason I had the prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Thibault,
Thanks for checking in on this ticket. It's helpful to get a clear
resolution rather than leaving things hanging in an unclear state.
On 12/01/2011 11:14 AM, Thibault Jouannic wrote:
> I'm looking for some news about the ticket #12635.
>
On Thu, Dec 1, 2011 at 10:14 AM, Thibault Jouannic wrote:
> Hi django devs,
>
> I'm looking for some news about the ticket #12635.
>
> https://code.djangoproject.com/ticket/12635
>
> Today, it's still impossible to easily access post data when sending a
> PUT request. Since I'm trying to build a
Hi django devs,
I'm looking for some news about the ticket #12635.
https://code.djangoproject.com/ticket/12635
Today, it's still impossible to easily access post data when sending a
PUT request. Since I'm trying to build a restful web service using
django, this is quite a problem.
It's been tol
12 matches
Mail list logo
