Mailman 3 May 2006 - Distutils-SIG

setuptools: hardcoding the path in a script and site.py
by Ian Bicking 18 May '06

18 May '06

So, there's really two monkeypatches to setuptools that workenv does to setuptools, and I'd like to get rid of them; they cause a lot of trouble, in part because setuptools is making it difficult to monkeypatch with the recent change to easy-install.pth (at least, I think it's a recent change) -- but if I don't need to monkeypatch setuptools then this won't be a problem, and I don't really need to be compatible with old versions of setuptools because workingenv can (maybe always should) install its own version of setuptools. The first is hardcoding paths in scripts. This is the monkeypatch: def get_script_header(script_text, executable=easy_install.sys_executable): from distutils.command.build_scripts import first_line_re first, rest = (script_text+'\\n').split('\\n',1) match = first_line_re.match(first) options = '' if match: script_text = rest options = match.group(1) or '' if options: options = ' '+options if options.find('-S') == -1: options += ' -S' shbang = \"#!%(executable)s%(options)s\\n\" % locals() shbang += ("import sys, os\\n" "join, dirname = os.path.join, os.path.dirname\\n" "lib_dir = join(dirname(dirname(__file__)), 'lib', 'python%s.%s' % tuple(sys.version_info[:2]))\\n" "sys.path.insert(0, lib_dir)\\n" "import site\\n") return shbang easy_install.get_script_header = get_script_header Basically we're creating: #!/usr/bin/python -S import sys, os join, dirname = os.p;ath.join, os.path.dirname lib_dir = join(dirname(dirname(__file__)), 'lib', 'python%s.%s' % tuple(sys.version_info[:2])) sys.path.insert(0, lib_dir) import site # the rest... I'm thinking this could be done with an installation option (that I can put in distutils.cfg), like: script_path_override = lib/python2.4 I'd prefer this path be interpreted relative to the location the script is installed (os.path.join(os.path.dirname(__file__), override)), but that doesn't fit with the typical way distutils interprets things. Two options? script_path_override, script_path_relative_override? This is also a feature Jim has requested for Zope. The other monkeypatch I'm doing is to keep setuptools from demanding to own site.py. The monkeypatch is: def install_site_py(self): # to heck with this, we gots our own site.py and we'd like # to keep it, thank you pass easy_install.easy_install.install_site_py = install_site_py But what would be better is if setuptools installed code somewhere besides site.py. For instance, site-setuptools.py. Then if site.py didn't exist, it would be created like: import os # add site-setuptools execfile(os.path.join(os.path.dirname(__file__), 'site-setuptools.py') If the file did exist, setuptools would check for the text "add site-setuptools", and give a warning or error if it was not, or maybe would just prefix the site.py with this text, and leave the rest of it as is. Then I'd include that code in workingenv's site.py. -- Ian Bicking / ianb(a)colorstudy.com / http://blog.ianbicking.org

1 1

Script processing plugins?
by Phillip J. Eby 18 May '06

18 May '06

Okay, so after today's discussions I'm still not really clear on how path freezing (baking, whatever) should work for standalone setuptools. Would it solve the problem for your use cases if I provided an option like "--script-wrappers=plugin1,plugin2,...", where the plugin names are entry points that would get a chance to modify the contents of generated scripts? That way, you guys could experiment freely with your script-wrapping strategies without having to monkeypatch. And any tools that you build which wrap easy_install can simply add the necessary setting(s) to an appropriate .cfg file.

3 3

Script-specific .pth files (or baking paths into scripts)
by Jim Fulton 17 May '06

17 May '06

I seem to remember a threat from from Phillip to make a proposal for installing script-specific ,pth files with scripts, but I don't think I every saw anything. Have I missed anything? If so, what? :) If not, I'll probably write something myself and share it. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

3 9

cross-compiling with distutils?
by Hollis Blanchard 15 May '06

15 May '06

Hi, I have a python module that uses distutils. I'm trying to build it on an x86 system for a PPC host. Through much digging, I've found that I can override CC to use my cross-compiler, but somehow it still wants to use CFLAGS like -march=i386. Also, the output directory is still "build/temp.linux-i686-2.4". I have seen a fair amount of python cross-compiling pain on the net, but few answers. Any help? Thanks! -- Hollis Blanchard IBM Linux Technology Center

1 0

Getting eggs from with user, password
by Mike Bernson 13 May '06

13 May '06

I want to use eggs for a non-open source project. What I would like to do is create a page that has all the eggs for the project but is password. I would then like easy_install to be able to access this page. I see an option for adding a url to look at for find eggs. What I am missing is a way to supply this user and password for download. Am I missing something here or is not possible to have password to protect the page where some eggs exist ?

3 2

Setuptools 0.6b1 released
by Phillip J. Eby 12 May '06

12 May '06

There are no new major features in this release, but many bug fixes and a few minor enhancements. From here on out, the 0.6 line is for bug fixes only; any new features will have to go into the 0.7 alpha trunk.

1 0

easy_install: #egg taking priority
by Ian Bicking 12 May '06

12 May '06

So, first the setup. We wanted to require PIL for a package. PIL goes by the name "PIL" and "Imaging". Specifically, the file you download is named "Imaging", and the actual package installed is named "PIL". You can install Imaging (as long as you use easy_install -f http://effbot.org/downloads/) , but it doesn't work as a requirement because Imaging itself does not fulfill an Imaging requirement. So, I figured we'd put in a link like this in someplace listed in -f (we have a local set of links we maintain): http://effbot.org/downloads/Imaging-1.1.5.tar.gz#egg=PIL-1.1.5 But, this doesn't work. easy_install pays attention to "Imaging-1.1.5.tar.gz" and ignores the "#egg=..." portion. This seems wrong, since the only reason for #egg to be there is to help easy_install, so it should take priority (or both names could be read, as long as the #egg info isn't thrown away). We worked around this by creating a shortened link with rubyurl.com (irony! tinyurl.com apparently doesn't allow non-browser user agents, and rubyurl was the next thing I could think of), and adding the #egg to that. A little silly and indirect, but a workaround for now. -- Ian Bicking / ianb(a)colorstudy.com / http://blog.ianbicking.org

2 1

Re: [Distutils] Getting eggs from with user, password
by Phillip J. Eby 12 May '06

12 May '06

At 04:11 PM 5/9/2006 -0400, Mike Bernson wrote: >I want to use eggs for a non-open source project. > >What I would like to do is create a page that has all the eggs for the >project but >is password. I would then like easy_install to be able to access this >page. I see an >option for adding a url to look at for find eggs. What I am missing is a >way to >supply this user and password for download. > >Am I missing something here or is not possible to have password to protect the >page where some eggs exist ? If you want to implement this in an upgrade tool of your own, you can subclass PackageIndex (in setuptools.package_index) and then use that as the package index for an easy_install command instance. You would need to have the download code check for a 401 and prompt the user to enter their ID and password. If you send me working code, I'll see if I can incorporate a similar feature back into the standard easy_install release, but I'd like to do it in such a way that easy_install remains non-interactive by default.

1 0

Re: [Distutils] easy_install finding wrong platform
by Phillip J. Eby 08 May '06

08 May '06

At 06:46 PM 5/8/2006 -0400, Charlie Moad wrote: >For matplotlib I have pypi's download url set to >"http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=…". > All the files are over the 5MB limit in case anyone asks. When I run >"easy_install -U matplotlib" on windows 2.4 it is downloading the >"matplotlib-0.87.2-py2.4-macosx10.4.mpkg.zip" file instead of >"matplotlib-0.87.2-py2.4-win32.egg". Obviously wrong. Hi Charlie; this is a known issue that is fixed in the SVN trunk and 0.6 branch of setuptools; released versions of easy_install are confused by "bdist_dumb" distributions of this sort, as they think the .zip file is of a project called "matplotlib" with a version of "0.87.2-py2.4-macosx10.4.mpkg", and since this is a higher version than "0.87.2" easy_install considers it a better match. I hope to release 0.6b1 shortly, which will fix this problem in the released version. In the meantime, you can "easy_install matplotlib==0.87.2" to work around the problem, or "easy_install setuptools==dev06" to upgrade to the SVN version of the 0.6 branch (soon to be released as 0.6b1).

1 0

easy_install finding wrong platform
by Charlie Moad 08 May '06

08 May '06

For matplotlib I have pypi's download url set to "http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=…". All the files are over the 5MB limit in case anyone asks. When I run "easy_install -U matplotlib" on windows 2.4 it is downloading the "matplotlib-0.87.2-py2.4-macosx10.4.mpkg.zip" file instead of "matplotlib-0.87.2-py2.4-win32.egg". Obviously wrong. Thanks, Charlie

1 0