[Distutils] easy_install of django sdist tarball omits data files
Hi I've been trying to install a sdist tarball of a django svn snapshot using easy_install but some of the packages data files (the admin contrib app templates) aren't being installed. I've looked at the easy_install web page and can't see anything that may help me install these data files. I'm doing this as part of a deployment script that uses easy_install to install a web apps dependencies into a particular directory. Is this a misuse of easy install? django's setup.py doesn't use setuptools and so easy_install seems to be creating an sdist_egg on the fly. I'm working round this by just scripting untarring, setup.py install etc. directly which is ok but it would be simpler if i could just call easy_install for all my apps dependencies. thanks, Graham ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] [Enthought-dev] Building Fedora RPMs
On Mon, 2007-10-22 at 18:15 -0500, Dave Peterson wrote: Stanley A. Klein wrote: Other failures included: endo - unpackaged pyc and pyo files (looks like a setup.py issue) I get rpms built for this just fine. Are you sure you have no local changes? The problem with this one may be a setuptools issue. The failure in doing the bdist_rpm is on a file endo.py, which is identified to setuptools in the setup.py as a script. The file is originally in enthought/endo/scripts. The pyc and pyo files get built there properly because of the [install] optimize=1 option in setup.cfg. However, the INSTALLED_FILES also lists a /usr/bin/endo.py without the pyc and pyo files. The Fedora rpm system causes those optimization files to be built unbeknownst to setuptools, which then causes the installed but unpackaged files error. I tried declaring the pyc and pyo files in the script statement, but at that point they don't exist and I got an error to that effect. There is probably a workaround, like commenting out the scripts statement in the setup.py and providing rpm a post-install script to copy endo.* into /usr/bin. However, it would create separate setup.py files for rpm and non-rpm packaging. Stan Klein On Mon, 2007-10-22 at 18:15 -0500, Dave Peterson wrote: Stanley A. Klein wrote: Other failures included: endo - unpackaged pyc and pyo files (looks like a setup.py issue) I get rpms built for this just fine. Are you sure you have no local changes? The problem with this one may be a setuptools issue. The failure in doing the bdist_rpm is on a file endo.py, which is identified to setuptools in the setup.py as a script. The file is originally in enthought/endo/scripts. The pyc and pyo files get built there properly because of the [install] optimize=1 option in setup.cfg. However, the INSTALLED_FILES also lists a /usr/bin/endo.py without the pyc and pyo files. Fedora causes those optimization files to be built unbeknownst to setuptools, which causes the installed but unpackaged files error. I tried declaring the pyc and pyo files in the script statement, but at that point they don't exist and I got an error to that effect. There is probably a workaround, like commenting out the scripts statement in the setup.py and providing rpm a post-install script to copy endo.* into /usr/bin. However, it would create separate setup.py files for rpm and non-rpm packaging. Stan Klein ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] [Enthought-dev] Building Fedora RPMs
Phillip J. Eby wrote: At 10:37 AM 10/23/2007 -0400, Stanley A. Klein wrote: On Mon, 2007-10-22 at 18:15 -0500, Dave Peterson wrote: Stanley A. Klein wrote: Other failures included: endo - unpackaged pyc and pyo files (looks like a setup.py issue) I get rpms built for this just fine. Are you sure you have no local changes? The problem with this one may be a setuptools issue. The failure in doing the bdist_rpm is on a file endo.py, which is identified to setuptools in the setup.py as a script. The file is originally in enthought/endo/scripts. The pyc and pyo files get built there properly because of the [install] optimize=1 option in setup.cfg. However, the INSTALLED_FILES also lists a /usr/bin/endo.py without the pyc and pyo files. The Fedora rpm system causes those optimization files to be built unbeknownst to setuptools, which then causes the installed but unpackaged files error. I tried declaring the pyc and pyo files in the script statement, but at that point they don't exist and I got an error to that effect. There is probably a workaround, like commenting out the scripts statement in the setup.py and providing rpm a post-install script to copy endo.* into /usr/bin. However, it would create separate setup.py files for rpm and non-rpm packaging. Better still, take off the '.py' on the 'endo' script, and/or use setuptools' script generation support. I'll take a stab at switching it to use the setuptools script support. -- Dave ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] [Enthought-dev] Building Fedora RPMs
Phillip J. Eby wrote: At 10:37 AM 10/23/2007 -0400, Stanley A. Klein wrote: On Mon, 2007-10-22 at 18:15 -0500, Dave Peterson wrote: Stanley A. Klein wrote: Other failures included: endo - unpackaged pyc and pyo files (looks like a setup.py issue) I get rpms built for this just fine. Are you sure you have no local changes? The problem with this one may be a setuptools issue. The failure in doing the bdist_rpm is on a file endo.py, which is identified to setuptools in the setup.py as a script. The file is originally in enthought/endo/scripts. The pyc and pyo files get built there properly because of the [install] optimize=1 option in setup.cfg. However, the INSTALLED_FILES also lists a /usr/bin/endo.py without the pyc and pyo files. The Fedora rpm system causes those optimization files to be built unbeknownst to setuptools, which then causes the installed but unpackaged files error. I tried declaring the pyc and pyo files in the script statement, but at that point they don't exist and I got an error to that effect. There is probably a workaround, like commenting out the scripts statement in the setup.py and providing rpm a post-install script to copy endo.* into /usr/bin. However, it would create separate setup.py files for rpm and non-rpm packaging. Better still, take off the '.py' on the 'endo' script, and/or use setuptools' script generation support. Thanks for pointing that out! I've just gotten the time to try modifing the endo project to use the setuptools' script generation -- went pretty easily btw. I can now successfully do a bdist_rpm on my CentOS5 system. -- Dave ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] [Enthought-dev] Building Fedora RPMs
On Tue, October 23, 2007 11:58 am, Dave Peterson wrote: Phillip J. Eby wrote: At 10:37 AM 10/23/2007 -0400, Stanley A. Klein wrote: On Mon, 2007-10-22 at 18:15 -0500, Dave Peterson wrote: Stanley A. Klein wrote: Other failures included: endo - unpackaged pyc and pyo files (looks like a setup.py issue) I get rpms built for this just fine. Are you sure you have no local changes? The problem with this one may be a setuptools issue. The failure in doing the bdist_rpm is on a file endo.py, which is identified to setuptools in the setup.py as a script. The file is originally in enthought/endo/scripts. The pyc and pyo files get built there properly because of the [install] optimize=1 option in setup.cfg. However, the INSTALLED_FILES also lists a /usr/bin/endo.py without the pyc and pyo files. The Fedora rpm system causes those optimization files to be built unbeknownst to setuptools, which then causes the installed but unpackaged files error. I tried declaring the pyc and pyo files in the script statement, but at that point they don't exist and I got an error to that effect. There is probably a workaround, like commenting out the scripts statement in the setup.py and providing rpm a post-install script to copy endo.* into /usr/bin. However, it would create separate setup.py files for rpm and non-rpm packaging. Better still, take off the '.py' on the 'endo' script, and/or use setuptools' script generation support. I'll take a stab at switching it to use the setuptools script support. From what Phillip says, all it might require is changing the name from endo.py to endo in both enthought/endo/scripts and the script statement in the setup.py file. The file already has a #!/usr/bin/python as its first line, so I think it can run as a command without producing the .pyo and .pyc files in /usr/bin that bother SE-Linux. I tried to do that and build the package, but I ran into problems of svn and setuptools remembering what was there before and I got worse errors. :-( I've had problems like that before. Stan Klein -- ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
