On 8/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > 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.)
There isn't one recipe. You first have to decide whether a particular API should use bytes or str. I would like to write something up because I know it will be important for maintainers of extension modules; but I don't have the time right now. > Also, given that we are close, shouldn't a few buildbots be set up? Agreed. Neal tried to set up a buildbot on the only machine he can easily use for this, but that's the "old gentoo box" where he keeps getting signal 32. (I suspect this may be a kernel bug and not our fault.) I forget who can set up buildbots -- is it Martin? Can someone else help? -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ 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