Closed simoncozens closed 1 year ago
Indeed I wonder if the changes to Py_UNICODE
are why I'm getting this build error:
/Users/simon/others-repos/emsdk/upstream/emscripten/cache/sysroot/include/c++/v1/__iterator/back_insert_iterator.h:35:15: error: 'container' declared as a pointer to a reference of type 'std::vector<wchar_t> &'
_Container* container;
^
src/openstep_plist/writer.cpp:4464:131: note: in instantiation of template class 'std::back_insert_iterator<std::vector<wchar_t> &>' requested here
std::copy<Py_UNICODE const *,std::back_insert_iterator<std::vector<Py_UNICODE> &> >(__pyx_v_s, (__pyx_v_s + __pyx_v_length), std::back_inserter<std::vector<Py_UNICODE> &>((__pyx_v_self->dest[0])));
Oh, just saw your message, which is relevant to #19 and #20. Good that I am not the only one 😀
looks like we need to get rid of the deprecated Py_UNICODE apis to make openstep-plist PEP 393 compliant and being able to build 3.12 wheels:
https://docs.python.org/3/c-api/unicode.html#deprecated-py-unicode-apis https://peps.python.org/pep-0393/
I suppose we can get away with using wchar_t
instead of Py_UNICODE
, with the related conversion functions to/from PyUnicode
These appear to be deprecated in 3.11: