| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
It appears that `Py_FileSystemDefaultEncodeErrors` is not part of the limited API, and PyPy does not have it. Since pybind11 does not have a wrapper for `PyUnicode_EncodeFSDefault` (the main reason I had switched to a `encode` call earlier), we need to call it ourselves manually.
|
Is this a problem only for the meson builds? |
Sorry, something went wrong.
|
I don't think so; I forgot to mention it was caused by #26992 according to the CI logs. |
Sorry, something went wrong.
|
Ahh, okay, I was wondering if it needed to be backported (and possibly prompt another release), but the line that is changing is only on main, so don't think so. |
Sorry, something went wrong.
|
Should we be concerned that this has no test coverage? |
Sorry, something went wrong.
|
That is definitely wrong; we probably lost coverage for compiled code in the move to Meson. |
Sorry, something went wrong.
|
Looking at the coverage for the file directly, it's not really uncovered, but partially covered. This probably partially because we don't do coverage on non-Linux, but I'm investigating some outdated settings in the test config. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR summary
It appears that Py_FileSystemDefaultEncodeErrors is not part of the limited API, and PyPy does not have it. This broke wheel building CI only, as PyPy isn't otherwise built.
Since pybind11 does not have a wrapper for PyUnicode_EncodeFSDefault (the main reason I had switched to a encode call earlier), we need to call it ourselves manually.
PR checklist