<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 30, 2010, at 8:51 PM, <a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Menlo; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">Rather than removing it, we could fix it, but the fact that no one seems<span class="Apple-converted-space"> </span><br>to be using it makes me think that no one with the expertise and<span class="Apple-converted-space"> </span><br>interest will step up to so.<br></span></span></blockquote></div><br><div>I don't actually know enough about the APIs in question to be sure, but my understanding is that the 'cfsupport' pyrex mess was added to paper over some holes in PyObjC, which have (long?) since been filled. At least, I can import all the functions from 'CFNetwork' that it looks like we would need (based on the information here <<a href="http://bit.ly/bQWC3J">http://bit.ly/bQWC3J</a>>).</div><div><br></div><div>If someone wanted to do a real CFNetwork-based reactor, I think this means we wouldn't need to maintain any of our own C code.</div><div><br></div></body></html>