Klaas van Schelven
Klaas van Schelven
> It looks like there's a test case that'd need updating... Indeed, but what would the desired behavior be? If I understand it correctly that test shows that the response...
Reading the discussion above it appears to me that the staleness is caused by a lack of response from @tomchristie on my question on how to proceed.
I've updated the failing test to be succeeding; this at least amounts to having an implicit test on the newly introduced behavior as more or less suggested by @jeking3
> If I understand it correctly that test shows that the response data of a request contains some Python objects (as opposed to pure json)... perhaps because of mocking at...
> how these can be done I was looking into it, there's "only 3" commits in which they were introduced but I had to conclude that I'm a bit out...
`channels_redis.pubsub.RedisPubSubChannelLayer` does not use `EVAL`, so for now that's a workable workaround (for me).
@tomchristie anything I could do to move this forward?
Stalebot go away On Mon, Apr 18, 2022, 13:57 stale[bot] ***@***.***> wrote: > This issue has been automatically marked as stale because it has not had > recent activity. It...
@pokken-magic / @matthewhegarty anything I can do to move this PR (or its sibbling) forward?
If breaking compatibility is your concern, would it be an idea to accept this PR on the 3.x branch (which you just closed) instead?