Ben Bangert wrote: > On Nov 10, 2005, at 2:05 PM, Ian Bicking wrote: > >> I wasn't sure, so I did it to be safe. It shouldn't effect anything. >> >>>> except it doesn't work when doing the sandbox install, and the >>>> exception comes during the sandbox phase. I'm not sure why a >>>> sandbox installation is happening (zip_safe is explicitly set to >>>> False)? >>> >>> easy_install runs all setup scripts in a sandbox, since it has no >>> way of knowing whether a given script is "safe" until it actually >>> runs it in the sandbox. Easier to ask forgiveness than permission, >>> you might say. :) >> >> >> But apparently that import doesn't work when in the sandbox. Why >> test it when setup() says explicitly that it isn't safe? > > > Even if it doesn't 'test' it, it would still need a sandbox to stick > the svn checkout in while it builds and installs it, no? (Not that I > have any clue how setuptools works, but this is just a guess)
The sandbox in this case is when setuptools runs setup.py with fake file routines, to see if the setup.py file writes things to weird locations. Now that I think about it, this isn't for zip-safe testing, but to test if setuptools can properly wrap this. I can understand why to do this when running a distutils setup.py file, but could this be surpressed for a setup.py file which imports from setuptools? I think it should be presumed that it is safe in that case. -- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
