Issue tracker cleanup: SVN-2079

2019-11-03 Thread Nathan Hartman
For this week's issue, SVN-2079 "utf8_tests.py should be made non- iso8859-1 specific": According to the issue tracker, the utf8_tests.py fail on non-iso8859- 1 systems and it seems that much smarter people than myself were stumped as to how to fix it. * This issue was reported in 2004. * In 2005

Re: Issue tracker cleanup: SVN-2079

2019-11-03 Thread Branko Čibej
On 03.11.2019 17:45, Nathan Hartman wrote: > For this week's issue, SVN-2079 "utf8_tests.py should be made non- > iso8859-1 specific": > > According to the issue tracker, the utf8_tests.py fail on non-iso8859- > 1 systems and it seems that much smarter people than myself were > stumped as to how to

Re: Issue tracker housecleaning: SVN-1804

2019-11-03 Thread Nathan Hartman
On Sun, Nov 3, 2019 at 12:56 AM Nathan Hartman wrote: > On Sat, Nov 2, 2019 at 4:00 AM Yasuhito FUTATSUKI > wrote: > >> >> >> > finally: >> >server.quit() >> > ]]] >> >> As I mentioned before (but I couldn't tell what I want, sorry), >> smtplib.SMTP.quit() can raise exception. If s

Re: Issue tracker cleanup: SVN-2079

2019-11-03 Thread Nathan Hartman
On Sun, Nov 3, 2019 at 4:35 PM Branko Čibej wrote: > On 03.11.2019 17:45, Nathan Hartman wrote: > > For this week's issue, SVN-2079 "utf8_tests.py should be made non- > > iso8859-1 specific": > > That test has two problems: first, it depends on the locale where it's > being run; and second, it's

Re: Issue tracker housecleaning: SVN-1804

2019-11-03 Thread Yasuhito FUTATSUKI
On 2019/11/04 8:16, Nathan Hartman wrote: On Sun, Nov 3, 2019 at 12:56 AM Nathan Hartman wrote: It seems there's another problem. Apparently the 'raise .. from' construct is Python 3+. Which means this breaks the mailer for Python 2.7. I found this when I tested on Python 2.7 earlier and the

Re: Issue tracker housecleaning: SVN-1804

2019-11-03 Thread Daniel Shahaf
Yasuhito FUTATSUKI wrote on Mon, Nov 04, 2019 at 11:13:38 +0900: > On 2019/11/04 8:16, Nathan Hartman wrote: > > On Sun, Nov 3, 2019 at 12:56 AM Nathan Hartman > > wrote: > > > It seems there's another problem. > > > > Apparently the 'raise .. from' construct is Python 3+. Which means > > this b

Re: Merging branches/swig-py3 to trunk

2019-11-03 Thread Daniel Shahaf
Branko Čibej wrote on Tue, Oct 22, 2019 at 21:39:23 +0200: > 1. we release 1.13.0 as planned next week when the soak period ends > (pending any last-minute critical bugs found, of course); > > 2. immediately after the 1.13.0 release, we merge the swig-py3 branch > to trunk; and, Anyone

Re: Merging branches/swig-py3 to trunk

2019-11-03 Thread Branko Čibej
On 04.11.2019 05:52, Daniel Shahaf wrote: > Branko Čibej wrote on Tue, Oct 22, 2019 at 21:39:23 +0200: >> 1. we release 1.13.0 as planned next week when the soak period ends >> (pending any last-minute critical bugs found, of course); >> >> 2. immediately after the 1.13.0 release, we merge th

Re: Issue tracker housecleaning: SVN-1804

2019-11-03 Thread Yasuhito FUTATSUKI
On 2019/11/04 13:50, Daniel Shahaf wrote: Yasuhito FUTATSUKI wrote on Mon, Nov 04, 2019 at 11:13:38 +0900: On 2019/11/04 8:16, Nathan Hartman wrote: On Sun, Nov 3, 2019 at 12:56 AM Nathan Hartman wrote: It seems there's another problem. Apparently the 'raise .. from' construct is Python 3+