Neal> The string/unicode merge is making good progress. There are less
Neal> than 400 references to PyString. Most of the references are in
Neal> about 5-10 modules. Less than 50 modules in the core have any
Neal> references to PyString. We still need help converting over to use
Neal> unicode. If you are interested in helping out, the spreadsheet is
Neal> the best place to look for tasks:
Neal>
http://spreadsheets.google.com/ccc?key=pBLWM8elhFAmKbrhhh0ApQA&hl=en_US&pli=1
As someone who hasn't participated in the string->unicode conversion up to
this point (not even looking at any of the hundreds of related checkins)
it's not at all obvious how to correctly replace PyString_* with PyUnicode_*
in any given situation. Is there some document somewhere that can be used
to at least give some hints? (I think I asked this before. I'm not sure I
got an answer.)
Also, given that we are close, shouldn't a few buildbots be set up?
Skip
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
