<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Bill,</div><br><blockquote type="cite"><span class="Apple-style-span" style="font-family: Arial, Helvetica, 'Luxi Sans', sans-serif; font-size: 14px; white-space: pre; "><div style="padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I'm having a lot of trouble getting setuptools to work correctly across</div><div style="padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">a variety of architectures. Right now, of the dozen or so Python
packages I use, yours is the only one one that seems deeply wedded to
setuptools. Is there any deep reason for that? I can't see one from
a quick scan of the code. Since I can't reliably get setuptools to
work, I thought I'd just "cp -r" the "vobject" subdirectory from your
source tar file. Do you think there would be any problems with that?<br></div></span></blockquote><br><div>To the best of my recollection, I'm not using setuptools APIs for resources in anything but tests.</div><div><br></div><div>Sincerely,</div><div>Jeffrey</div><div><br></div><div><br></div></body></html>