Implementing RFCs 2387 and 2392
"Sunny K." <[email protected]> Fri, 8 Nov 2013 12:42:42 +0530
| Newsgroups | gmane.comp.python.mime.devel |
|---|---|
| Message-ID | <CAHT-KCq1T9o-nW1xWgmtqq=cg0=DsGtQE5HREWAd904CiZ8S1Q@mail.gmail.com> |
--===============1440751818== Content-Type: multipart/alternative; boundary=089e0111ae3424527a04eaa51e5c --089e0111ae3424527a04eaa51e5c Content-Type: text/plain; charset=ISO-8859-1 Hey, Are issues 634412[1] and 626452[2] still valid? I would like to work on them. Advice or caveats on how to work on them would be helpful. [1] http://bugs.python.org/issue634412 [2] http://bugs.python.org/issue626452 Thank You. --089e0111ae3424527a04eaa51e5c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div>Hey,<br><br></div>Are issues 634412[1] and 62645= 2[2] still valid? I would like to work on them. Advice or caveats on how to= work on them would be helpful.<br><br></div><div>[1] <a href=3D"http://bug= s.python.org/issue634412">http://bugs.python.org/issue634412</a><br> [2] <a href=3D"http://bugs.python.org/issue626452">http://bugs.python.org/i= ssue626452</a><br><br></div>Thank You.<br><br></div> --089e0111ae3424527a04eaa51e5c-- --===============1440751818== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline