[Python-Dev] Need help fixing failing Py3k Unittests in py3k-struni

[Chris McDonough]

I have a very remedial question about how to fix test failures due to  
the side effects of string-unicode integration.

The xmlrpc library uses explicit encoding to encode XML tag payloads  
to (almost always) utf8.  Tag literals are not encoded.

What would be the best way to mimic this behavior under the new  
regime?  Just use unicode everywhere and encode the entire XML body  
to utf-8 at the end?  Or deal explicitly in bytes everywhere?  Or..?

Remedially,

- C

On Jul 10, 2007, at 5:14 PM, Guido van Rossum wrote:

> One of the most daunting tasks remaining for Python 3.0a1 (to be
> released by the end of August) is fixing the remaining failing unit
> tests in the py3k-struni branch
> (http://svn.python.org/view/python/branches/py3k-struni/).
>
> This is the branch where I have started the work on the
> string/unification branch. I want to promote this branch to become the
> "main" Py3k branch ASAP (by renaming it to py3k), but I don't want to
> do that until all unit tests pass. I've been working diligently on
> this task, and I've got it down to about 50 tests that are failing on
> at least one of OSX and Ubuntu (the platforms to which I have easy
> access). Now I need help.
>
> To facilitate distributing the task of getting the remaining tests to
> pass, I've created a wiki page:
> http://wiki.python.org/moin/Py3kStrUniTests . Please help! It's easy
> to help: (1) check out the py3k-struni branch; (2) build it; (3) pick
> a test and figure out why it's failing; (4) produce a fix; (5) submit
> the fix to SF (or check it in, if you have submit privileges and are
> confident enough).
>
> In order to avoid duplicate work, I've come up with a simple protocol:
> you mark a test in the wiki as "MINE" (with your name) when you start
> looking at it. You mark it as "FIXED [IN SF]" once you fix it, adding
> the patch# if the fix is in SF. If you give up, remove your lock,
> adding instead a note with what you've found (even just the names of
> the failing subtests is helpful).
>
> Please help!
>
> There are other tasks, see PEP 3100. Mail me if you're interested in
> anything specifically. (Please don't ask me "do you think I could do
> this" -- you know better than I whether you're capable of coding at a
> specific level. If you don't understand the task, you're probably not
> qualified.)
>
> -- 
> --Guido van Rossum (home page: http://www.python.org/~guido/)
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/lists 
> %40plope.com
>