In this case, the current po is passed to the next invokation of parse so its content is not recreated with the new value of response. I was talking with @Gallaecio about this and while I think this behavior is not wrong, it took me a while to figure out why I was not getting new data in po until I realised my poor decision.
So, I think this should be allowed because there may be a case where someone want to pass and already created Poet Object instead of expecting a new one to be created. Nevertheless, as this is a quite rare case, maybe the library could log a warning to let the user know that he may be doing something wrong in most of the other cases.
I was working on a project where I manually had to retry some requests like:
In this case, the current
po
is passed to the next invokation ofparse
so its content is not recreated with the new value ofresponse
. I was talking with @Gallaecio about this and while I think this behavior is not wrong, it took me a while to figure out why I was not getting new data inpo
until I realised my poor decision.So, I think this should be allowed because there may be a case where someone want to pass and already created Poet Object instead of expecting a new one to be created. Nevertheless, as this is a quite rare case, maybe the library could log a warning to let the user know that he may be doing something wrong in most of the other cases.