On 30 January 2014 09:45, Vinay Sajip <vinay_sajip@yahoo.co.uk> wrote:
So much heat over process, but so little light over exactly why *appropriately designed* software deployed in wheels shouldn't be importable.
Good point. In my view, *appropriately designed* software is fine, and a metadata flag is a good idea. Although obviously that makes "mounting" a little more complex (check the flag) and argues for a mount method rather than people just fiddling sys.path. There's a lot of leeway for dispute over "appropriate design" and who gets to say, but that's not a technical issue. My one technical issue is with going beyond zipimport behaviour to the point of extracting DLLs to the filesystem. I remain -1 on that feature, and I believe I have explained why I think there are issues (and why I think that any solution should be part of zipimport and not added on in library or user code). But I'm happy to go through the details again, if you like - or just to accept that I don't need to use the feature. (Would you be willing to add some sort of "never extract C extensions regardless of what the metadata might say" option to wheel mount? It's not critical, as mounting random wheels without knowing how they work is clearly bad, but it does add a level of assurance that might be helpful,) The remaining issues seem to be mainly of education and expectations - people coming from non-Python (particularly Java) backgrounds have a set of assumptions that aren't easy to translate into Python terms. That's definitely not a technical problem. Paul.