From sunfinite at gmail.com Fri Nov 8 08:12:42 2013 From: sunfinite at gmail.com (Sunny K.) Date: Fri, 8 Nov 2013 12:42:42 +0530 Subject: [Email-SIG] Implementing RFCs 2387 and 2392 Message-ID: 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sunfinite at gmail.com Mon Nov 11 09:43:25 2013 From: sunfinite at gmail.com (Sunny K.) Date: Mon, 11 Nov 2013 14:13:25 +0530 Subject: [Email-SIG] Fwd: Implementing RFCs 2387 and 2392 In-Reply-To: References: Message-ID: Resending. The first mail does not seem to have gotten through. ---------- Forwarded message ---------- From: Sunny K. Date: 8 November 2013 12:42 Subject: Implementing RFCs 2387 and 2392 To: email-sig at python.org 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rdmurray at bitdance.com Mon Nov 11 17:59:26 2013 From: rdmurray at bitdance.com (R. David Murray) Date: Mon, 11 Nov 2013 11:59:26 -0500 Subject: [Email-SIG] Fwd: Implementing RFCs 2387 and 2392 In-Reply-To: References: Message-ID: <20131111165927.7869425007F@webabinitio.net> On Mon, 11 Nov 2013 14:13:25 +0530, "Sunny K." wrote: > Resending. The first mail does not seem to have gotten through. I got it, perhaps it was held for moderation initially. > 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 Yes these issues are still valid. The implementation of them will be (should be?) affected by the changes that just landed in the provisional email package code. In particular, the new code does contains some support that is directed at rfc 2387. Full support, as I currently envision it, involves a contentmanager that will turn a related into a dictionary object indexed by cid, and vice versa. The way I have this currently planned, any such support should go into a content manager released first as a third party library on pypi. The contentmanager code itself is still fresh, and won't leave provisional status until 3.5. If an enhanced content manager exists on pypi before then, it might be a candidate for inclusion as provisional in 3.5, depending on what the "state of play" looks like by that point. So, take a look at the new content manager code and the RFCs, and let us know your thoughts or questions. It is quite possible there is still some necessary infrastructure that is missing in the 3.4 email package code that will be discovered by implementing this support, and if so it would be nice to fix that in 3.5. --David From mark at msapiro.net Mon Nov 11 18:24:47 2013 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 11 Nov 2013 09:24:47 -0800 Subject: [Email-SIG] Fwd: Implementing RFCs 2387 and 2392 In-Reply-To: References: Message-ID: <528112DF.5060002@msapiro.net> On 11/11/2013 12:43 AM, Sunny K. wrote: > Resending. The first mail does not seem to have gotten through. See the Mailman FAQ article at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan