Mailman 3 May 2009 - Distutils-SIG

Re: [Distutils] PEP 376 up-to-date
by P.J. Eby May 27, 2009

May 27, 2009

At 11:01 AM 5/26/2009 +0200, Tarek Ziadé wrote: >Just one point though: > >- do we want to scan egg-info directories that are *directly* added in >sys.path ? No. Such a directory does not represent an importable egg on sys.path. If you mean an .egg file or directory that's directly on sys.path, then that's a bit different. Are you planning to support those? In that event you would need another EggInfo subclass anyway, and you could have the directory (or "PathEntry", perhaps?) constructor simply wrap a single such EggInfo in that event. Or, you can handle it the way pkg_resources does, which is to convert target paths into PEP 302 importer objects, and then use the importer's type to determine what sort of handler should be used for it.

2 1

[issue72] easy_install violates SELinux policies
by Jonathan Cervidae May 26, 2009

May 26, 2009

New submission from Jonathan Cervidae <jonathan.cervidae(a)gmail.com>: I get AVC's aftef installing egg's with easy_install. The AVS are that the files are mislabeled as: unconfined_u:object_r:user_tmp_t:s0 When I we want them to be: system_u:object_r:lib_t:s0 It stops python from accessing the files. I haven't looked at the source code, but those contexts suggest that easy_install is downloading the egg file to a temp directory then moving (not copying) it from the temp dir to /usr/lib/python<VERSION>/site-packages. This is clearly a good thing as unnecessary copying should be avoid and it's easy to fix too. I notice there is a python module called selinux installed on my system. So you need to try and import that. If you succeed you can try and restore the context after moving it to the new location and just ignore any error on that too. ---------- files: fix.txt messages: 292 nosy: jcervidae priority: bug status: unread title: easy_install violates SELinux policies Added file: http://bugs.python.org/setuptools/file53/fix.txt _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue72> _______________________________________________

1 0

Re: [Distutils] Side by side debug/non-debug eggs
by P.J. Eby May 22, 2009

May 22, 2009

At 12:00 PM 5/22/2009 -0400, Jean-Paul Calderone wrote: >On Fri, 22 May 2009 11:33:54 -0400, "P.J. Eby" <pje(a)telecommunity.com> wrote: >>At 09:45 AM 5/22/2009 -0400, Jean-Paul Calderone wrote: >>>Hello all, >>> >>>Prior to eggs, if I wanted to have debug and non-debug versions of an >>>extension module available, I could build and install the extension >>>twice and the modules would happily co-exist, for example: >>> >>> >>> $ python setup.py build install >>> ... >>> $ python-dbg setup.py build install >>> ... >>> $ .../site-packages/twisted/python$ ls *.so >>> _epoll_d.so _epoll.so >>> $ .../site-packages/twisted/python$ >>>If I then ran a debug build of Python, the debug extension would be loaded. >>>When I ran a normal build of Python, the non-debug extension would >>>be loaded. >>>However, with eggs, each new egg completely replaces the last egg. There >>>seems to be no possibility for side-by-side builds. Am I overlooking a >>>feature of eggs or of setuptools? >> >>Have you tried "setup.py develop"? This builds extensions in-place >>in the source tree and adds the source tree to sys.path. > >Aware of it, but I haven't tried it. In this use, it sounds very >similar to "setup.py build_ext -i", which also partially solves the >problem. Unfortunately, some packages have their source laid out >such that they cannot actually be used in-place, only after they've >been installed. The only other thing I can think of is installing in backward-compatibility mode, i.e. "setup.py install --single-version-externally-managed" (with a filename given to --record).

1 0

Re: [Distutils] [Trac] Re: Help packaging plugin : Source distribution
by P.J. Eby May 22, 2009

May 22, 2009

At 12:43 PM 5/22/2009 -0500, Olemis Lang wrote: >On Thu, May 21, 2009 at 3:56 PM, P.J. Eby <pje(a)telecommunity.com> wrote: > > At 11:15 AM 5/20/2009 -0500, Olemis Lang wrote: > >> > >> On Wed, May 20, 2009 at 10:09 AM, Jeff Hammel <jhammel(a)openplans.org> > >> wrote: > >> > > >> > You have to verbosely include them with package data. IMHO, this is a > >> > setuptools bug. E.g.: > >> > > >> > package_data={ 'geotrac': ['templates/*', 'htdocs/*'] }, > >> > include_package_data=True, > >> > > >> > This is probably not quite right :(, but you get the idea. > >> > >> I just tried this and doesnt include files for sdist ... :( > >> > >> Looking forward for further hints : maybe it's just something I'm > >> doing wrong, dont know, but eggs are ok so I'm not sure > > > > If you are not using a revision control system plugin, you will > have to list > > sdist files in MANIFEST.in; > >Thanks, I included files in MANIFEST.in now I can distribute source >packages for TracGViz [1]_ & TracPyTppTheme [2]_ so that EGGs can be >built for different Py versions or whatever ... > >So this is the way ! > >PS: BTW , I dont get the idea about specifying things twice (I mean >package_data & MANIFEST.in ;) Is there a «logical» reason for this ? I >mean why sdist doesnt look for the data specified in package_data ? Or >alternately, what is the reason for having MANIFEST.in too ? That's what distutils does. setuptools improves on it by adding revision control support. But if you don't use a revision control plugin or some other sort of file finder, you have to do it the old distutils way.

1 0

Re: [Distutils] Side by side debug/non-debug eggs
by P.J. Eby May 22, 2009

May 22, 2009

At 09:45 AM 5/22/2009 -0400, Jean-Paul Calderone wrote: >Hello all, > >Prior to eggs, if I wanted to have debug and non-debug versions of an >extension module available, I could build and install the extension >twice and the modules would happily co-exist, for example: > > > $ python setup.py build install > ... > $ python-dbg setup.py build install > ... > $ .../site-packages/twisted/python$ ls *.so > _epoll_d.so _epoll.so > $ .../site-packages/twisted/python$ >If I then ran a debug build of Python, the debug extension would be loaded. >When I ran a normal build of Python, the non-debug extension would be loaded. >However, with eggs, each new egg completely replaces the last egg. There >seems to be no possibility for side-by-side builds. Am I overlooking a >feature of eggs or of setuptools? Have you tried "setup.py develop"? This builds extensions in-place in the source tree and adds the source tree to sys.path.

3 3

how to set cc correctly?
by rupert.thurner May 22, 2009

May 22, 2009

how could one set the compiler correctly? http://opencsw has a setuptools package, which does not use the cc in the path, but in /opt/studio/SOS11/SUNWspro/bin/cc so the following happens: # CC=/opt/SUNWspro/bin/cc easy_install genshi Searching for genshi Reading http://pypi.python.org/simple/genshi/ Reading http://genshi.edgewall.org/ Reading http://genshi.edgewall.org/wiki/Download Best match: Genshi 0.5.1 Downloading http://ftp.edgewall.com/pub/genshi/Genshi-0.5.1.zip Processing Genshi-0.5.1.zip Running Genshi-0.5.1/setup.py -q bdist_egg --dist-dir /tmp/ easy_install-7yiT65/Genshi-0.5.1/egg-dist-tmp-Cp42JQ warning: no previously-included files found matching 'doc/ 2000ft.graffle' warning: no previously-included files matching '*' found under directory 'doc/logo.lineform' unable to execute /opt/studio/SOS11/SUNWspro/bin/cc: No such file or directory ********************************************************************** WARNING: An optional C extension could not be compiled, speedups will not be available. ********************************************************************** Adding Genshi 0.5.1 to easy-install.pth file Installed /opt/csw/lib/python2.6/site-packages/Genshi-0.5.1-py2.6- solaris-2.10-sun4v.egg Processing dependencies for genshi Finished processing dependencies for genshi

3 15

Side by side debug/non-debug eggs
by Jean-Paul Calderone May 22, 2009

May 22, 2009

Hello all, Prior to eggs, if I wanted to have debug and non-debug versions of an extension module available, I could build and install the extension twice and the modules would happily co-exist, for example: $ python setup.py build install ... $ python-dbg setup.py build install ... $ .../site-packages/twisted/python$ ls *.so _epoll_d.so _epoll.so $ .../site-packages/twisted/python$ If I then ran a debug build of Python, the debug extension would be loaded. When I ran a normal build of Python, the non-debug extension would be loaded. However, with eggs, each new egg completely replaces the last egg. There seems to be no possibility for side-by-side builds. Am I overlooking a feature of eggs or of setuptools? Thanks, Jean-Paul

1 0

Re: [Distutils] easy_install picks windows egg on Linux
by P.J. Eby May 21, 2009

May 21, 2009

At 01:49 PM 5/21/2009 -0400, Jean-Paul Calderone wrote: >Downloading >http://pypi.python.org/packages/2.5/p/pyOpenSSL/pyOpenSSL-0.9.py2.5-winxp32… What's bizarre is that that's not a valid egg filename; they must have renamed it at some point. The filename is invalid in two ways: first, it has a '.' between the version and the Python version (it should be a '-') and second, 'winxp32' is not a valid platform name. I would suggest contacting the PyOpenSSL maintainers to find out why they have renamed it in this fashion; .egg files should never be renamed under any circumstances. (I'm actually surprised that easy_install is recognizing it at all, but basically it appears to be treating it as if it's a non-platform-specific egg. That's arguably a bug.) >zipimport.ZipImportError: not a Zip file This part is an expected failure with a --dry-run. It perhaps could be fixed, but the problem is that with --dry-run on, the egg is not moved to the target directory, so when it tries to create a Distribution object for the installed egg, it fails. This has nothing to do with the version problem - you will probably see this occur at the end of any --dry-run install, unless an identically-named egg was was already present.

2 1

[issue71] type of renamed eggs misdetected by easy_install
by Jean-Paul Calderone May 21, 2009

May 21, 2009

New submission from Jean-Paul Calderone <exarkun(a)twistedmatrix.com>: Due to user error, an egg which should have been a Python 2.5 Windows binary egg got renamed to "pyOpenSSL-0.9.py2.5-winxp32.egg" and uploaded to PyPI. easy_install will select this egg for installation on Linux, though it is not usable on that platform. ---------- messages: 290 nosy: exarkun priority: bug status: unread title: type of renamed eggs misdetected by easy_install _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue71> _______________________________________________

1 0

easy_install picks windows egg on Linux
by Jean-Paul Calderone May 21, 2009

May 21, 2009

Hi all, I just noticed that easy_install selects a Windows binary egg when trying to install pyOpenSSL on Linux. Predictably, this fails: $ PYTHONPATH=/tmp/junk6 easy_install --install-dir /tmp/junk6 --dry-run pyOpenSSL Creating /tmp/junk6/site.py Searching for pyOpenSSL Reading http://pypi.python.org/simple/pyOpenSSL/ Reading http://pyopenssl.sourceforge.net/ Reading http://launchpad.net/pyopenssl Best match: pyOpenSSL 0.9.py2.5 Downloading http://pypi.python.org/packages/2.5/p/pyOpenSSL/pyOpenSSL-0.9.py2.5-winxp32… Processing pyOpenSSL-0.9.py2.5-winxp32.egg Moving pyOpenSSL-0.9.py2.5-winxp32.egg to /tmp/junk6 Traceback (most recent call last): File "/usr/bin/easy_install", line 8, in <module> load_entry_point('setuptools==0.6c8', 'console_scripts', 'easy_install')() File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 1671, in main with_ei_usage(lambda: File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 1659, in with_ei_usage return f() File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 1675, in <lambda> distclass=DistributionWithoutHelpCommands, **kw File "/usr/lib/python2.5/distutils/core.py", line 151, in setup dist.run_commands() File "/usr/lib/python2.5/distutils/dist.py", line 974, in run_commands self.run_command(cmd) File "/usr/lib/python2.5/distutils/dist.py", line 994, in run_command cmd_obj.run() File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 211, in run self.easy_install(spec, not self.no_deps) File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 446, in easy_install return self.install_item(spec, dist.location, tmpdir, deps) File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 476, in install_item dists = self.install_eggs(spec, download, tmpdir) File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 619, in install_eggs return [self.install_egg(dist_filename, tmpdir)] File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 696, in install_egg return self.egg_distribution(destination) File "/usr/lib/python2.5/site-packages/setuptools/command/easy_install.py", line 661, in egg_distribution metadata = EggMetadata(zipimport.zipimporter(egg_path)) zipimport.ZipImportError: not a Zip file exarkun@charm:/tmp$ Is this a known issue? Jean-Paul

1 0