-------------------------------------------- On Thu, 30/1/14, Paul Moore <p.f.mo...@gmail.com> wrote:
> I'm still not comfortable with the temp directory clutter that unpacking > leaves (in particular on Windows where deletion isn't even possible > in an atexit routine) but I'll survive. It's up to the using application to do cache management of this type. It's not as if the cache will grow unbounded in most realistic scenarios, and perfectly possible to do cleanup during startup. It may not be ideal, but seems acceptable given the limitations of the underlying platform. > I *would* like to see the various technical issues and implications in > the API documentation, though. The implications and limitations, and > in particular the manual cache management requirements, need to be > made explicit. (I thought I'd seen docs somewhere, but they definitely > aren't in the API reference for the distlib.wheel module). There's some mention in the distlib.resources documentation (the cache would also be used for things like cacert.pem), but I'll certainly update the wheel documentation to cover this area, and update the relevant parts of the distlib.resources and distlib.util documentation, too. BTW, I raised the whole issue of extracting C extensions for import from zips on python-dev in March last year: https://mail.python.org/pipermail/python-dev/2013-March/124970.html The feedback I got indicated (to me) that while people felt there were some problem areas (e.g. cleanup was mentioned), there were no show-stoppers. No ringing endorsements, but no red flags were raised either. Regards, Vinay Sajip _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
