Message210366
| Author |
serhiy.storchaka |
| Recipients |
Arfrever, georg.brandl, larry, richard, serhiy.storchaka, vajrasky |
| Date |
2014年02月06日.08:32:13 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<2785835.NrSBrs9ESk@raxxla> |
| In-reply-to |
<1391673629.84.0.490928556656.issue20517@psf.upfronthosting.co.za> |
| Content |
> This issue has been on my radar for a while (originally #16074). But I
> wasn't paying strong attention to it. Nobody in that issue came up with a
> solution I liked. Finally when you posted your patch I said "ugh, can't we
> do better" and had to think about it before I realized we should just
> display both filenames. If somebody had posted a patch with that two
> months ago I would have happily accepted it and we wouldn't be having this
> conversation now.
Actually that was Vajrasky's patch, and that was extended version of your
patch. I asked you not because you are release manager, but because you are
the author of the code and original patch.
I agree that support errors with two filenames is better solution than remove
ambiguous filename attribute, but there is no much time left and we still don't
have a patch. Vajrasky's patch is alternate variant for 3.4 in case when
better patch will not be ready and is only solution for 3.3 (if we decide to
fix this in 3.3). |
|