Sebastian Pipping

@jsummers to avoid misunderstandings, the plan was to provide a pull request for you so you would not need to "do" anything in the sense of building things and the...

@jsummers okay, I consider https://github.com/projectM-visualizer/frontend-libvisual-plug-in/blob/master/.github/workflows/linux.yml more of a YAML shell script rather than magic, but I will not push for it any further then, I understand and respect the need...

Hi @LilSpazJoekp is my understanding correct that this worked with 4.3.0 for you previously? I'm not sure right now what we can do about these requests not being deepcopy-able. Maybe...

@LilSpazJoekp I see, thanks for the clarification :+1:

@LilSpazJoekp potentially important to know: If this is fixed it will be fixed in a release VCR.py >=5.0.1 with support for >=Python 3.8 only. Your CI shows still shows use...

@jairhenrique that makes more sense now. Do we really want to have a pull request hang around for that long though? It may need constant rebasing for nothing, long-lived pull...

@jairhenrique if it works for you I'm good, okay.

If after a rebase CI is all green, this can be merged. If it's not, it may be the same issue as back then, more details at https://github.com/kevin1024/vcrpy/pull/699#issuecomment-1551439663 .

@dgw I'm not 100% sure what you mean. We can only merge things that are fully green, if there is unrelated breakage elsewhere, that breakage needs dedicated fixing outside of...

> @hartwork I mean that every commit with a check status on `master` has been ❌ since [c9da7a1](https://github.com/kevin1024/vcrpy/commit/c9da7a102fe5b260c0341a5fdf693123f19845a2), and I have never been able to cleanly build this patch because...