Mailman 3 March 2010 - Distutils-SIG

Re: [Distutils] bdist_rpm with different python version
by P.J. Eby 25 Mar '10

25 Mar '10

At 12:01 PM 3/24/2010 -0700, Aaron Brice wrote: >I am working on a RHEL5 system with python 2.4 installed as >/usr/bin/python and python 2.6 installed as /usr/bin/python2.6. > >When I run "python2.6 setup.py install" in a module it generally does >the right thing and installs to /usr/lib/python2.6/site-packages/. So >I want to generate a rpm to deploy the module, but "python2.6 setup.py >bdist_rpm" does not do the right thing, the .spec file generated uses >"python" and not "python2.6" and the resulting rpm installs to >/usr/lib/python2.4/site-packages/. > >Is there a way to override this behavior? The --fix-python option hardcodes the path to the currently-running python. Run "setup.py bdist_rpm --help" for more details.

1 0

bdist_rpm with different python version
by Aaron Brice 25 Mar '10

25 Mar '10

I am working on a RHEL5 system with python 2.4 installed as /usr/bin/python and python 2.6 installed as /usr/bin/python2.6. When I run "python2.6 setup.py install" in a module it generally does the right thing and installs to /usr/lib/python2.6/site-packages/. So I want to generate a rpm to deploy the module, but "python2.6 setup.py bdist_rpm" does not do the right thing, the .spec file generated uses "python" and not "python2.6" and the resulting rpm installs to /usr/lib/python2.4/site-packages/. Is there a way to override this behavior? Thanks, Aaron

1 0

repeatable and updatable virtualenv
by Chris Withers 25 Mar '10

25 Mar '10

Hi All, How can I set up a virtualenv in such a way that I can version control the packages and their versions that are installed in it? The answer would appear to a custom bootstrap script, but how would I think update an existing virtualenv when I added or removed packages or changed the version of a specific package? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

10 18

Re: [Distutils] repeatable and updatable virtualenv
by a.cavallo＠cavallinux.eu 23 Mar '10

23 Mar '10

Hi, there's my little project running on the opensuse build server. Actually it builds the latest subversion of python under the opt tree using the best practices in the field (nearly hands-off approach, integrating unit testing, repeatable etc). http://pyvm.sourceforge.net You can get an account and build the modules linking to these builds (automatically and overnight). Regards, Antonio Cavallo Disclaimer. I'm the author and the only maintainer. For a living I work in QA if that matters to you. On Tue 23/03/10 11:21, "Lennart Regebro" regebro(a)gmail.com wrote: > On Mon, Mar 22, 2010 at 09:59, Chris Withers <chris@ > simplistix.co.uk> wrote: > Saint Germain wrote: > >> > >> I'm currently trying more or less the same thing > by combining buildout >> with virtualenv and pip. > > > > This doesn't seem like a sane thing to > do. > Sure it does. It's just not very useful in most cases. Buildout by > itself works fine to isolate the python installation from the stuff > installed. > But if you want to also isolate the buildout from what's installed in > the python, then you can use virtualenv for that. > > Unusual usecase, but sane. :) > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG(a)python.org > http://mail.python.org/mailman/listinfo/distutils-sig > >

1 0

problem with bdist_msi post-install script
by Bill Janssen 23 Mar '10

23 Mar '10

When I try to include a post-install script in my MSI built with bdist_msi, it seem to be included and unpacked properly, but it doesn't run successfully. Here's what's in the script (after unpacking): #!c:\Python26\python.exe # do nothing much import sys, os, time print "Hello, World" time.sleep(10) sys.exit(0) And here's what I get in my install log (generated with "msiexec /i foo.msi /L*v foo.log"): Action 18:35:46: install_script. Action start 18:35:46: install_script. MSI (s) (40:E0) [18:35:46:882]: Note: 1: 1722 2: install_script 3: C:\Python26\\python.exe 4: C:\Python26\Scripts\foo-install-script.py MSI (s) (40:E0) [18:35:46:882]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (FC:78) [18:35:46:902]: Note: 1: 2262 2: Error 3: -2147287038 DEBUG: Error 2835: The control ErrorIcon was not found on dialog ErrorDlg The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDlg, Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action install_script, location: C:\Python26\\python.exe, command: C:\Python26\Scripts\foo-install-script.py MSI (s) (40:E0) [18:35:50:978]: Note: 1: 2262 2: Error 3: -2147287038 Any ideas? What's a postinstall script supposed to return or exit with to indicate success or failure, anyway? What does "The control ErrorIcon was not found on dialog ErrorDlg" mean? Bill

3 14

[buildout] selectively excluding site-packages
by Chris Withers 22 Mar '10

22 Mar '10

Hi Guys, I guess this is mainly aimed at Jim and Gary... How's the work to allow control over which packages come from site-packages and whether or not site-packages is considered by default? Anything I can do to help with this? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

5 11

Re: [Distutils] [buildout] How to configure python interpreter to use it with Google Appengine?
by Tres Seaver 21 Mar '10

21 Mar '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Максим Lacrima wrote: > Thanks! You have pointed the right direction. > I have had to add following list of paths in order to make custom > interpreter work as expected: > .../parts/google_appengine > .../parts/google_appengine/lib/antlr3 > .../parts/google_appengine/lib/django > .../parts/google_appengine/lib/ipaddr > .../parts/google_appengine/lib/webob > .../parts/google_appengine/lib/yaml/lib > > Thanks again for the help! Glad that worked! Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkulOIsACgkQ+gerLs4ltQ41nQCgu3ej6tVq4aVuQlxVYdnoouXP vLQAnidB1HkJuJIzgwajeAo9SXpcC2Zu =VRzi -----END PGP SIGNATURE-----

1 0

How to specific metadata version in setup.py?
by Sridhar Ratnakumar 21 Mar '10

21 Mar '10

My package's PKG-INFO defaults to 1.0 metadata version. I tried searching http://docs.python.org/distutils/ to know how to specify 1.2 as the metadata version (so I can include Classifiers[1], maintainer* fields in it), but couldn't find any. Does anyone know? Shouldn't this be documented in http://docs.python.org/distutils/setupscript.html which talks about these additional fields in section 2.8? -srid [1] Evidently, some packages in PyPI do not have 'Classifiers' in their metadata (PKG-INFO) despite specifying it in the setup.py.

3 10

Re: [Distutils] [buildout] How to configure python interpreter to use it with Google Appengine?
by Tres Seaver 21 Mar '10

21 Mar '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Максим Lacrima wrote: > Thanks for your reply, Tres! Here is my buildout.cfg: > [buildout] > develop = . > parts = python test appengine > > [python] > recipe = zc.recipe.egg:scripts > interpreter = python > eggs = unikeeper > > [test] > recipe = pbp.recipe.noserunner > eggs = unikeeper > working-directory = ./src/keeper > > [appengine] > recipe = rod.recipe.appengine > eggs = unikeeper > server-script = dev_appserver > exclude = unit_tests > doc_tests > unikeeper.egg-info > url = http://googleappengine.googlecode.com/files/google_appengine_1.3.1.zip It looks as though the google_appengine zipfile doesn't intend to be installed in such a way as to make its libraries easily usable under setuptools. The rod.recipe.appenge recipe creates the script for running the development environment, and puts 'parts/google_appengine' on sys.path. I think you could use the 'extra-paths' argument to the 'zc.recipe.eggs:scripts' recipe to add that same path to your custom interpreter, like so: [python] recipe = zc.recipe.eggs:scripts interpreter = python eggs = unikeeper extra-paths = ${buildout:directory}/parts/google_appengine Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkulAoIACgkQ+gerLs4ltQ5WNwCfXEfFucLseXXgWiFJIZVp1XMS ih0AnRW+1pf9SqakrjkW1R6HiTlIaV5T =hM5r -----END PGP SIGNATURE-----

1 0

[buildout] How to configure python interpreter to use it with Google Appengine?
by Максим Lacrima 21 Mar '10

21 Mar '10

Hello! I use buildout to develop my Google Appengine application. To set up GAE I use rod.recipe.appengine. Thanks to this recipe I can deploy my application, use development server etc. Also I want my Python interpreter to access this environment, so I can import appengine's webapp, db and so on. I don't know how to do this. Currently I have next configuration of the interpreter: [python] recipe = zc.recipe.egg:scripts interpreter = python eggs = myapp With this configuration I can't access any part of google_appengine. What should I do to properly customize Python interpreter for use with Appengine. Thanks in advance. Sorry, if my English isn't proper enough. with regards, Maxim

2 1