I just tried to install the egg for Pyx, and got the error pasted below. I've contacted the mailing list for that project, and they seem to be unsure of where they can put shared data for their egg. The error message below says that I should contact the maintainers of the package (which I have done) and the EasyInstall maintainers for a workaround. So, is there a workaround for this?
Thanks,
Mike Hearne
Running PyX-0.10/setup.py -q bdist_egg --dist-dir /tmp/easy_install- _D_bmc/PyX-0.10/egg-dist-tmp-r1bHsH error: Setup script exited with error: SandboxViolation: mkdir('/usr/ local/share/pyx',) {}
The package setup script has attempted to modify files on your system that are not within the EasyInstall build area, and has been aborted.
This package cannot be safely installed by EasyInstall, and may not support alternate installation locations even if you run its setup script by hand. Please inform the package's author and the EasyInstall maintainers to find out if a fix or workaround is available.
------------------------------------------------------ Michael Hearne mhearne@usgs.gov (303) 273-8620 USGS National Earthquake Information Center 1711 Illinois St. Golden CO 80401 Senior Software Engineer Synergetics, Inc. ------------------------------------------------------
At 12:34 PM 4/22/2008 -0600, Michael Hearne wrote:
I just tried to install the egg for Pyx, and got the error pasted below. I've contacted the mailing list for that project, and they seem to be unsure of where they can put shared data for their egg.
Eggs do not have shared data -- they only have runtime-accessible data, because they're not a distribution format in the way that system packages are.
However, the problem in this case is that PyX isn't using any of the standard distutils ways to install these files. If they were using the standard install_data command, the data would at least be shipped inside the egg.
If they were using the package_data facility, however (which available in Python 2.4 and up), they would be able to include the files inside their package (and thus the egg) and be able to access them using either __file__-relative paths or the pkg_resources API.
Any of these approaches would work, and unless they need to support Python 2.3, would probably be easier to use than their current method of creating a siteconfig.py file. Their setup.py would then not need to include any custom distutils commands, as it does now.
(And such a change would not require any reliance on setuptools, either.)
participants (2)
-
Michael Hearne -
Phillip J. Eby