Woodrow Douglass
Woodrow Douglass
I'm happy to refactor to resolve this, but let's discuss a solution first.
> Hey @wdouglass > > Sorry I never responded to this. I am just starting to catch up on things for `v3.1.0`. I think we should remove `Unknown` entirely. This...
yeah, i could try to put a patch together later today
Ok, fair enough. I've filed a bug against pygobject here (i've also referenced this patch, i hope that's OK) https://gitlab.gnome.org/GNOME/pygobject/-/issues/519
unfortunately, this bug seems to just get kicked back and forth between glib and pygobject. I'm gonna keep running with the workaround from this PR; i don't think either of...
investigating glib as a source of this problem https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2478 if that ends up getting merged to glib, i'll close this issue
I wonder if we can unexpose p1.Payload, and have some kind of copy-on-write semantics (just because i think writing into the payload of an unmarshalled packet like this is kind...
As an update, i've written a PR for the pygobject library that also addresses this issue https://gitlab.gnome.org/GNOME/pygobject/-/merge_requests/219
careful merging this though, because if/when the pygobject fix gets merged, you'll have a ref underflow for systems that have an updated pygobject...
> UTF-8 should not be used as a reference, as it's a much more complicated encoding. Does it match ASCII? It does also match ascii