On Sun, Mar 30, 2008 at 5:54 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote: > If you have the time to figure it all out, sure. > I found that quite a tedious task, and had to spent > on some patches quite a long time to figure out what > they do, and what the 3.x equivalent should be. > Is there any easy way that the burden of trunk -> py3k merging could be moved to the original committers of the trunk patches? Presumably the original committer of a patch is well-placed to understand what the patch does and how best to translate it to 3.0. Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20080330/fe0f6db6/attachment.htm
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4