* Dave O'Neill <[EMAIL PROTECTED]> [2008-06-27T10:30:10] > On Thu, Jun 26, 2008 at 01:37:09PM -0400, Ricardo SIGNES wrote: > > Content-Type: multipart/related; boundary=xyzzy; type=foo > > Content-Type: text/plain; boundary=xyzzy; type=foo > > The docs for make_singlepart say "Also crunches 0-part multiparts into > singleparts", so the first option is probably the safest for backwards > compatibility. However, it does seem nonsensical to convert an empty > multipart/* part into a text/plain. Is this a case that's frequently > encountered? If not, maybe it's OK to change that behavior.
I think that it's documented, so it should keep working. If nobody has asked for it to throw an error, it either isn't coming up or it's coming up and people accept it. I'd suggest adding an error-generating branch (with a different method name or an arg) or just removing the entire Content-* header set (since there is no content!) but I wouldn't need to use it, and who knows if anyone else would. I think the only problematic behavior is the bizarre (and presumably illegal) leftover parameters. -- rjbs
