You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 27, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 27, 2018. It is now read-only.
I am using Python 2.7.
I got 4 outputs when I check response.text before if-branch for DELETE and 1 output of response.text inside of if-branch, for example:
Interesting. It appears as though when a DELETE call is made, the response
is essentially empty, which makes reasonable sense. The JSON decoder
doesn't handle an empty string, hence it triggering an exception. This
should be a lot easier to filter on than a non-empty, non-JSON response. I
think I'd like to propose instead of having the conditional filter on the
request_type (which seems somewhat hokey and artificial), it should filter
on whether or not the response has any text at all in it. Each API method
call can return None if no response was received, and the decoded response
otherwise. I will see if I can't make that change in a branch tomorrow
morning (it's really late here, currently), and you can give it a go.
Activity
rpcope1 commentedon Oct 21, 2015
Can you dump what response.text has in it when DELETE is called?
rpcope1 commentedon Oct 21, 2015
Also, can you give me what the traceback on that was, as well as the version of Python you are using?
yangyixizg commentedon Oct 22, 2015
I am using Python 2.7.
I got 4 outputs when I check response.text before if-branch for DELETE and 1 output of response.text inside of if-branch, for example:
rpcope1 commentedon Oct 22, 2015
Interesting. It appears as though when a DELETE call is made, the response
is essentially empty, which makes reasonable sense. The JSON decoder
doesn't handle an empty string, hence it triggering an exception. This
should be a lot easier to filter on than a non-empty, non-JSON response. I
think I'd like to propose instead of having the conditional filter on the
request_type (which seems somewhat hokey and artificial), it should filter
on whether or not the response has any text at all in it. Each API method
call can return None if no response was received, and the decoded response
otherwise. I will see if I can't make that change in a branch tomorrow
morning (it's really late here, currently), and you can give it a go.
On Thu, Oct 22, 2015 at 12:15 AM, yixiyangh notifications@github.com
wrote:
Issue #9 - Some delete bodies are empty, and json deserialization fails.
rpcope1 commentedon Nov 5, 2015
Sorry, this slipped under my radar a little bit. I just pushed a fix that may hopefully fix this.
yangyixizg commentedon Nov 9, 2015
super, thx for updating, it is fixed now. May I ask you if you would extend the your PythonConfluenceAPI by an other authentication, e.g. NTLM?
rpcope1 commentedon Nov 9, 2015
I'm not immediately sure how to do that, but I'll look into it.
On Mon, Nov 9, 2015 at 4:32 AM, yixiyangh notifications@github.com wrote: