Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RcjQk-0007ZV-OD for bitcoin-development@lists.sourceforge.net; Mon, 19 Dec 2011 20:03:26 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.47 as permitted sender) client-ip=209.85.213.47; envelope-from=jordanmack1981@gmail.com; helo=mail-yw0-f47.google.com; Received: from mail-yw0-f47.google.com ([209.85.213.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1RcjQf-0000OA-7m for bitcoin-development@lists.sourceforge.net; Mon, 19 Dec 2011 20:03:26 +0000 Received: by yhoo47 with SMTP id o47so4568328yho.34 for ; Mon, 19 Dec 2011 12:03:15 -0800 (PST) Received: by 10.236.146.36 with SMTP id q24mr10863574yhj.85.1324324995880; Mon, 19 Dec 2011 12:03:15 -0800 (PST) Received: from [192.168.0.50] (c-67-188-239-72.hsd1.ca.comcast.net. [67.188.239.72]) by mx.google.com with ESMTPS id n24sm31677051yhj.13.2011.12.19.12.03.13 (version=SSLv3 cipher=OTHER); Mon, 19 Dec 2011 12:03:14 -0800 (PST) Sender: Jordan Mack Message-ID: <4EEF987D.7060404@parhelic.com> Date: Mon, 19 Dec 2011 12:03:09 -0800 From: Jordan Mack User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com> <201112191315.25857.luke@dashjr.org> <4EEF8806.6070707@parhelic.com> <201112191416.56029.luke@dashjr.org> In-Reply-To: <201112191416.56029.luke@dashjr.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.4 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (jordanmack1981[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (jordanmack1981[at]gmail.com) 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1RcjQf-0000OA-7m Subject: Re: [Bitcoin-development] [BIP 15] Aliases X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 20:03:26 -0000 I wish that was the case. It would have made my life a lot easier in the past. A lot of the MIME libraries out there are extremely buggy. MIME is just difficult to work with, and support is still weak. Undefined content length + text based boundaries = pain in the ass. It is in the e-mail module because that's all MIME was originally intended for. It's now grown beyond that now, but you will find the MIME functions still live in the e-mail libraries. When dealing with raw MIME encoded data, e-mail is still the most common case. On 12/19/2011 11:16 AM, Luke-Jr wrote: > MIME has been around much longer, and should have sufficient support in every > language by now. For some reason, Python calls the module 'email'.