Re: Python 3 branch

--===============8894342123958794170==
Content-Type: multipart/alternative; boundary="00000000000001cb9f05e7e04d14"

--00000000000001cb9f05e7e04d14
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> With the sudden flurry of emails about SpamBayes, I went ahead and
created a new python3 branch at
>
> https://github.com/smontanaro/spambayes
>
> This is the result of a basic run of 2to3 nearly two years ago (!)
followed by most functional changes to Neil Schemenauer's Python 3 partial
port:
>
> https://github.com/nascheme/spambayes-core/
>
> Nothing has been tested. I haven't even tried running anything yet. Given
that I use Gmail, I suspect I will have to try getting the IMAP filter to
run to make it semi-useful.

I'm focusing on sb_imapfilter, mostly because that is what would be most
immediately useful to me (as a Gmail user).

I fairly quickly got the app to start and launch its web server (in
spambayes/Dibbler.py), then ran into a raft of byte/str problems. No
surprise there, I suppose. After a few rounds of that (edit, run, poke a
link, see a traceback, lather, rinse, repeat) I began to wonder if there
was a better way. A couple things occur to me:

   - Is there a way to coax the server to =E2=80=94 early on =E2=80=94 deco=
de incoming
   bytes as utf-8?
   - Would it be better to see about replacing the Dibbler, asyncore, and
   asynchat modules with stdlib modules? Note that the async* modules aren'=
t
   even the old stdlib versions =E2=80=94 may not even have anything in com=
mon with
   them other than their names.

Any thoughts?

Skip

--00000000000001cb9f05e7e04d14
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt; With the sudden flurry of emails about SpamBayes, I w=
ent ahead and created a new python3 branch at<br>&gt;<br>&gt; <a href=3D"ht=
tps://github.com/smontanaro/spambayes">https://github.com/smontanaro/spamba=
yes</a><br>&gt;<br>&gt; This is the result of a basic run of 2to3 nearly tw=
o years ago (!) followed by most functional changes to Neil Schemenauer&#39=
;s Python 3 partial port:<br>&gt;<br>&gt; <a href=3D"https://github.com/nas=
cheme/spambayes-core/">https://github.com/nascheme/spambayes-core/</a><br>&=
gt;<br>&gt; Nothing has been tested. I haven&#39;t even tried running anyth=
ing yet. Given that I use Gmail, I suspect I will have to try getting the I=
MAP filter to run to make it semi-useful.<br><br><div>I&#39;m focusing on s=
b_imapfilter, mostly because that is what would be most immediately useful =
to me (as a Gmail user).</div><div><br></div><div>I fairly quickly got the =
app to start and launch its web server (in spambayes/Dibbler.py), then ran =
into a raft of byte/str problems. No surprise there, I suppose. After a few=
 rounds of that (edit, run, poke a link, see a traceback, lather, rinse, re=
peat) I began to wonder if there was a better way. A couple things occur=C2=
=A0to me:</div><div><ul><li>Is there a way to coax the server to =E2=80=94 =
early on =E2=80=94 decode incoming bytes as utf-8?</li><li>Would it be bett=
er to see about replacing the Dibbler, asyncore, and asynchat modules with =
stdlib modules? Note that the async* modules aren&#39;t even the old stdlib=
 versions =E2=80=94 may not even have anything in common with them other th=
an their names.</li></ul><div><div class=3D"gmail_default" style=3D"font-fa=
mily:arial,sans-serif">Any thoughts?</div><div class=3D"gmail_default" styl=
e=3D"font-family:arial,sans-serif"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,sans-serif">Skip</div><br></div></div></div>

--00000000000001cb9f05e7e04d14--

--===============8894342123958794170==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
spambayes-dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/spambayes-dev

--===============8894342123958794170==--