Showing content from http://mail.python.org/pipermail/python-dev/attachments/20120311/c68feaef/attachment.html below:
<br><br><div class="gmail_quote">On Sat, Mar 10, 2012 at 22:16, PJ Eby <span dir="ltr"><<a href="mailto:pje@telecommunity.com">pje@telecommunity.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div class="im">On Sat, Mar 10, 2012 at 5:49 PM, Thomas Wouters <span dir="ltr"><<a href="mailto:thomas@python.org" target="_blank">thomas@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>(And, yes, I'm zipping up the stdlib for Python 2.7 at Google, to reduce the impact on the aforementioned million of machines :)</div></blockquote><div><br></div></div><div>You might want to consider instead backporting the importlib caching facility, since it provides some of the zipimport benefits for plain old, non-zipped modules. Â Actually, a caching-only import hook that operated that way wouldn't even need the whole of importlib, just a wrapper over the standard C import that skips the unnecessary filesystem accesses.</div>
</div>
</blockquote></div><br>Thanks for the suggestions (Antoine too), but that's not really the topic I want to discuss here (but if you guys move to Google I'll happily discuss all the stuff we have to deal with.) The questions is really whether Python wants to actually support zipped stdlibs or not.<br clear="all">
<div><br></div>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!<br>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4