Mailman 3 June 2010 - Distutils-SIG

[buildout] develop vs extends/default.cfg
by Chris Withers 29 Jun '10

29 Jun '10

Hi All, What is the expected behaviour when the following are all true: - default.cfg has a develop key - buildout.cfg has a develop key, and extends a base.bfg - base.cfg has a develop key My hope is that all 3 should be set unioned for the develop options. However, my experience so far is that, at the least, the one in default.cfg is ignored... Chris

2 4

How does buildout determine paths needed? (for django-page-cms)
by John Griessen 29 Jun '10

29 Jun '10

I made a buildout with the config below that didn't work right and found it needed to have some extra paths added. Here is the extra path I needed: '/home/john/buildout/eggs/django_page_cms-1.1.3-py2.6.egg', '/home/john/buildout/eggs/django_page_cms-1.1.3-py2.6.egg/pages/templates/pages', pages was being found to not have the contents wanted. Is having a dir pages and pages/templates/pages a naming problem for buildout? If a search is being done for * in pages, it might stop short when the top level pages is found. Hints, suggestions how to resolve this appreciated. Meanwhile, every time I run buildout, I'll need to copy an paste that extra path... John -----buildout.cfg---- [buildout] eggs-directory = /home/john/buildout/eggs extensions = mr.developer parts = django eggs = mock django-notification django-page-cms django-haystack django-staticfiles django-messages django-mptt-2 whoosh [django] recipe = djangorecipe version = 1.2.1 settings = development wsgi = true eggs = ${buildout:eggs} project = industromatic_com --------buildout.cfg----------

2 1

bdist_wininst compatibility with pythons and windows versions
by anatoly techtonik 27 Jun '10

27 Jun '10

While Trac 0.12 is about to be released, there is some uncertainty whenever new Distutils-generated installers are compatible with old versions of Windows and Python. There are some fears that installers generated on Vista and Windows 7 won't run on XP or 2000. Is that true? Also is there a limit on the lowest version of Python that installer generated with Distutils to say 2.6.5 will run? [1] http://trac.edgewall.org/ticket/9404#comment:7 [2] http://scons.tigris.org/issues/show_bug.cgi?id=2533 -- anatoly t.

4 8

Test failure: test_python_53586
by Michael Foord 25 Jun '10

25 Jun '10

Hello all, When I do a *full test run* of py3k I get a distutils test failure. It doesn't happen if I run test_distutils on its own: bigmac:py3k michael$ ./python.exe -m test.regrtest -j12 == CPython 3.2a0 (py3k:82215, Jun 25 2010, 13:59:00) [GCC 4.2.1 (Apple Inc. build 5659)] == Darwin-10.4.0-i386-64bit == /compile/py3k/build/test_python_53586 ... lots of results skipped test test_distutils failed -- Traceback (most recent call last): File "/compile/py3k/Lib/distutils/tests/support.py", line 16, in _capture_warnings return func(*args, **kw) File "/compile/py3k/Lib/distutils/tests/test_sysconfig.py", line 47, in test_get_python_inc self.assertTrue(os.path.isdir(inc_dir), inc_dir) AssertionError: /compile/py3k/build/test_python_53586/Include All the best, Michael Foord -- http://www.voidspace.org.uk

2 2

comparing version strings?
by Chris Withers 25 Jun '10

25 Jun '10

Hi All, Is there any any in setuptools/distutils/anything else that I can use to compare version strings using the same rules as setuptools? ie: sort the following list of versions: 1.0 2.0dev-r22542-20100623 2.0dev-r22553-20100624 2.0 ...etc cheers, Chris

4 4

buildout behavior as source revisions change
by John Griessen 24 Jun '10

24 Jun '10

Some weeks ago I made a buildout config using mr.developer and djangorecipe extensions that worked to get a svn trunk version of django-mptt and now it stops with an error message. Is there a way to specify sources better so it still works when a rev number changes? Do I have a syntax error? The place it has trouble with is rev=>0.2.2 Now I think I can do without the svn version since django-mptt is now at 0.3.0. $ bin/buildout output from past the error message ------------------------------------------ Getting distribution for 'django-mptt-2>0.2.1'. zip_safe flag not set; analyzing archive contents... mptt.tests.settings: module references __file__ mptt.tests.test_runner: module references __file__ Got django-mptt-2 0.3.0. ---------------------------------- The Getting line above says the rev=>0.2.2 didn't get used anyway? Know why not? Is this a mr.developer problem? Please give my buildout config a look and suggest how I can learn this better. The config and the error output follow. Thanks, John ------------------- [buildout] eggs-directory = /home/john/buildout/eggs extensions = mr.developer sources = sources auto-checkout = django-mptt parts = django eggs = mock django-notification django-page-cms django-haystack django-messages [sources] django-mptt = svn http://django-mptt.googlecode.com/svn/trunk/ rev=>0.2.2 path=src-untouched [django] recipe = djangorecipe version = 1.1.1 settings = development wsgi = true eggs = ${buildout:eggs} project = cottagematic_com ---------------------------------- comand line output -------------------------- john@toolbench:~/WEBprojects/cottagematic_bld$ bin/buildout Getting distribution for 'mr.developer'. Got mr.developer 1.14. Page at http://pypi.python.org/simple/argparse/ links to .py file(s) without version info; an index scan is required. Getting distribution for 'argparse'. zip_safe flag not set; analyzing archive contents... Got argparse 1.1. mr.developer: Queued 'django-mptt' for checkout. Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib/python2.6/threading.py", line 532, in __bootstrap_inner self.run() File "/usr/lib/python2.6/threading.py", line 484, in run self.__target(*self.__args, **self.__kwargs) File "/home/john/buildout/eggs/mr.developer-1.14-py2.6.egg/mr/developer/common.py", line 99, in worker output = action(**kwargs) File "/home/john/buildout/eggs/mr.developer-1.14-py2.6.egg/mr/developer/svn.py", line 263, in checkout matches = self.matches() File "/home/john/buildout/eggs/mr.developer-1.14-py2.6.egg/mr/developer/svn.py", line 298, in matches return (info.get('url') == url) and (int(info.get('revision')) > int(rev[1:])) ValueError: invalid literal for int() with base 10: '0.2.2' <snip>

1 1

[buildout] zc.buildout.testing.install(_develop) and test setup slowness
by Chris Withers 24 Jun '10

24 Jun '10

Hi All, Can anyone explain how or why zc.buildout.testing.install and zc.buildout.testing.install_develop don't install the dependencies of the package you specify? I'm writing a recipe that requires the Zope2 package to be present, and it has rather a lot of dependent packages. The pattern with buildout recipe tests seems to be to manually install the package under test with zc.buildout.testing.install_develop and then each required package with zc.buildout.testing.install. For Zope2, this doesn't scale so well ;-) Also, even doing the manual install above is *really* slow, I have a test that now takes 20-30 seconds before it even starts running :-( Any ideas how to make this situation better? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

2 4

Buildout not working with Bash wrapper for `python'
by Gustavo Narea 24 Jun '10

24 Jun '10

Hello, I have a Bash script that wraps our custom-compiled Python interpreter to set a couple of required variables, but Buildout is failing to install dependencies when that wrapper is used. The Bash script looks like this: ---- #!/bin/bash export PYTHONHOME="${HOME}/.twod/pythons/2.5.5" export LD_LIBRARY_PATH="${PYTHONHOME}/lib:${LD_LIBRARY_PATH}" exec ${PYTHONHOME}/bin/python "$@" --- It works like a charm for everything but Buildout. This is what I get when I run it with log-level=DEBUG: --- ... Getting required 'django-audit==1.0b1' required by foo. We have no distributions for django-audit that satisfies 'django-audit==1.0b1'. Getting distribution for 'django-audit==1.0b1'. Running easy_install: /bin/bash /home/gustavo/.twod/pythons/2.5.5/bin/python-wrapper "-c" "from setuptools.command.easy_install import main; main()" "-mUNxd" "/home/gustavo/.twod/pythons/2.5.5/buildout-eggs/tmp4binwi" "-Z" "-q" "/home/gustavo/.buildout/downloads/dist/django-audit-1.0b1.tar.gz" path=/home/gustavo/System/Pyenvs/twod-trunk/eggs/distribute-0.6.13-py2.5.egg An error occured when trying to install django-audit 1.0b1. Look above this message for any errors that were output by easy_install. While: Installing. Getting section scripts. Initializing section scripts. Getting option scripts:initialization. Getting section twod_vars. Initializing part twod_vars. Getting distribution for 'django-audit==1.0b1'. Error: Couldn't install: django-audit 1.0b1 --- If I run manually the command Buildout is running, it works: /bin/bash /home/gustavo/.twod/pythons/2.5.5/bin/python-wrapper "-c" "from setuptools.command.easy_install import main; main()" "-mUNxd" "/home/gustavo/.twod/pythons/2.5.5/buildout-eggs/tmp4binwi" "-Z" "-q" "/home/gustavo/.buildout/downloads/dist/django-audit-1.0b1.tar.gz" Why doesn't it work within Buildout? How can I make it give a more detailed description of the error? I have the following in buildout.cfg: --- [buildout] ... executable = /bin/bash /home/gustavo/.twod/pythons/2.5.5/bin/python-wrapper --- Thanks in advance. PS: I need to set $PYTHONHOME and $LD_LIBRARY_PATH because we require Python 2.5.5 with --enable-shared. -- Gustavo Narea. Software Developer. 2degrees, Ltd. <http://dev.2degreesnetwork.com/>.

6 9

Including test and docs in distribution
by Michael Foord 22 Jun '10

22 Jun '10

Hey all, I have a single module I distribute and I would *like* to include the tests (a package) and docs (sphinx generated - single directory) in the distribution - but not have them "installed" by setup.py. Is this possible with either distutils or distribute? Anyone able to suggest the right magic incantation for the setup.py? (Or a better approach - I really don't want to make my 600 line single module a package though.) All the best, Michael Foord -- http://www.voidspace.org.uk

3 3

Buildout: Funky syntax for Extending sections (macros)
by Suresh V. 19 Jun '10

19 Jun '10

Why does buildout use the "<=" syntax for this? Wouldn't it be nicer to just overload "extends"? I do appreciate this feature! Suresh

2 3