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; 
Sender: Jordan Mack <jordanmack1981@gmail.com>
Message-ID: <4EEF987D.7060404@parhelic.com>
Date: Mon, 19 Dec 2011 12:03:09 -0800
From: Jordan Mack <jordanmack@parhelic.com>
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
Subject: Re: [Bitcoin-development] [BIP 15] Aliases
Precedence: list

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'.