Message63652
| Author |
belopolsky |
| Recipients |
alexandre.vassalotti, belopolsky, dgreiman |
| Date |
2008年03月17日.15:29:53 |
| SpamBayes Score |
0.5408801 |
| Marked as misclassified |
No |
| Message-id |
<d38f5330803170829o201bd9bdma3893796cfa2ea34@mail.gmail.com> |
| In-reply-to |
<1205761885.38.0.0694702171213.issue2298@psf.upfronthosting.co.za> |
| Content |
On Mon, Mar 17, 2008 at 9:51 AM, Alexandre Vassalotti <
report@bugs.python.org> wrote:
>
> Alexandre Vassalotti <alexandre@peadrop.com> added the comment:
>
> .. Although I haven't reviewed this
> patch yet, I find the naming of the `ustr` variable confusing -- e.g. is
> it a bytes object or a unicode object?
There is no `ustr` variable , you probably mean `uarg`. If so, it is
not introduced by the patch. To me the patch looks straightforward and
correct, but a unit test should be added. Some additional refactoring is
due for getargs.c (does py3k support builds without Py_USING_UNICODE?), but
the bug fix should not wait for that. |
| Files |
|---|
| File name |
Uploaded |
|
unnamed
|
belopolsky,
2008年03月17日.15:29:53
|
|