Mailman 3 July 2008 - Distutils-SIG

HTML files are included in code coverage analysis
by Gustavo Narea 19 Jul '08

19 Jul '08

Hello, everyone. If I run `setup.py unittest', everything works (http://paste.turbogears.org/paste/3279), but if I run it with the following options: --xml-output build/test-results.xml --coverage-summary \ build/test-coverage.txt --coverage-dir build/coverage it fails because it includes *.html files in the code coverage: http://paste.turbogears.org/paste/3280 How can I avoid that HTML files are included in the code coverage analysis? I couldn't find the answer via `./setup.py unittest --help' Here's my repository https://svn.gnulinuxmatters.org:81/animador/trunk/ and here you can browse the source code: https://tracker.gnulinuxmatters.org/browser/animador/trunk Thanks in advance. -- Gustavo Narea. General Secretary. GNU/Linux Matters. http://www.gnulinuxmatters.org/

1 0

[buildout] New buildout release that recompiles and can always unzip
by Jim Fulton 19 Jul '08

19 Jul '08

I just made a new release of zc.buildout, 1.1.0, that: - Provides a global buildout option, unzip, that sets the default policy for unzipping eggs. If you include: unzip = true in your buildout section, then all eggs will be unzipped by default. Note that you'll need zc.recipe.egg 1.1.0 or later for this to work for eggs installed by the egg recipes. - Now recompile Python files when eggs are installed unzipped. This is helpful for debugging, as the file names stored in code objects will be correct. Both pyc and pyo files are produced. (Most eggs only have pyc files.) Jim -- Jim Fulton Zope Corporation

1 0

[zc.buildout] general doc sprawl
by Chris Withers 18 Jul '08

18 Jul '08

Hi All, If you go to http://pypi.python.org/pypi/zc.buildout/1.0.6 the resulting page is *huge* :-( There doesn't appear to be any real structure to it and it reads as if it's been added to by various different authors over time. It also seems to be a good example of "doctests gone wrong" where the doc has become less important than the test. Of particular difficulty is that sections often seem to refer to concepts that are only introduced further down in the document. As someone trying to learn buildout in depth, what I'd most like is: - a short tutorial introduction (this bit is there, I think..) - a list/reference of the options passable when running buildout (I think this appears about 30% of the way through that doc, but I'm not sure all the options are covered) - a list/reference of the "commands" buildout has. I counted "install" and "init" and maybe "bootstrap" too, but I don't know if that's all and I'm still hazy about what the differences are between each one. - a list/reference of the options names that have meaning in the [buildout] section to buildout itself. There seem to be a *lot* of these and they're scattered throughout the document at that URL. I have a horrible sinking feeling that I'm going to spend most of my life with buildout trying to find the right option name to use :-/ - now, and now only, docs on how to write recipes and then on to the more esoteric stuff, although I suspect the references above would likely cover a lot of it. It'd also be great it it wasn't just one monolithic file, but I guess that's just my reading preference :-S I'm afraid I'm unable to offer resources to try and fix this problem but I do feel it should be highlighted as it makes buildout, which now that I'm finally getting over the documentation barrier, seems to actually be a very sturdy and useful tool (and gets over some of the setuptools, egg and pypi suck), exponentially less easy to play with for newbies. Oh, and a parting shot: it would be great to get some idea of the "known good" recipe types to use too. I see the plone guys have vomited several million recipe eggs into pypi and, to be blunt, it's impossible to figure out which were written by muppets and which by people with functioning brains. Someone mentioned a cmmi recipe at EPC. That sounded interesting but now I don't know where to find it... drowning-ly yours, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 4

[zc.buildout] init/bootstrap commands
by Chris Withers 18 Jul '08

18 Jul '08

Hi All, Is it just be or would it be better if: - the bootstrap command also copied the latest bootstrap.py into the new buildout? - the bootstrap and init commands were combined? I can't see where they're useful on their own... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 3

[zc.buildout/egg-cache] .pyc files referencing temporary location?
by Andreas Jung 16 Jul '08

16 Jul '08

We have some reports from co-workers working with zc.buildout and an egg-cache where the .pyc files refer to temporary directories within the egg-cache (obviously the location where the files within the egg were unpacked and compiled) - something like that. P:\home\freyp\.buildout\eggs\tmp27l-TE\Products.LDAPUserFolder-2.5-py2.4.egg\Products\LDAPUserFolder\LDAPUserFolder.py" Is there some solution other than removing the .pyc files? The issue seems to be related to debugging Zope environments with WingIDE. Andreas -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting

3 2

Scripts and configuration data
by Lumír Jasiok 16 Jul '08

16 Jul '08

Hi, I am developing small package that provide some Python package and some other data (scripts and configuration data). I know how to install script(s), bud I have no idea how to install configuration file(s) using setuptools. For example I have configuration file called "kiosk.conf" and I want to install it into "/etc/kiosk/" directory. So I have to create /etc/kiosk/ dir (if isn't already exists) and put the file into. How can I do this? Lumir -- Lumír Jasiok VSB-TU Ostrava - Computer centre E-mail: lumir.jasiok(a)vsb.cz http://www.vsb.cz

1 0

[zc.buildout] repeatable buildouts
by Chris Withers 16 Jul '08

16 Jul '08

wow, I'm on a roll tonight ;-) So: http://pypi.python.org/pypi/zc.buildout/1.0.6#repeatable-buildouts-controll… I just don't really follow this... Is the 'versions' name in the [buildout] section meaningful to buildout? what are the keys in a version section? just egg versions or something else? fwiw, most of the time I seem to use an egg recipe or something similar to lock specific egg versions. Having the release number in the section name seems odd, I'd expect something more like [buildout] versions = versions [versions] spam = 1 eggs = 2.2 ...and then just keep the versions stuff correct on different svn branches/tags of the buildout. What am I missing? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

3 10

[zc.recipe.egg] why would eggs get updated when not specified?
by Chris Withers 16 Jul '08

16 Jul '08

Reading this: http://pypi.python.org/pypi/zc.recipe.egg#egg-updating So, the eggs options is removed from the recipe. Why then would the demo egg be updated towards the end of the section? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 2

[zc.buildout] bootstrap.py
by Chris Withers 16 Jul '08

16 Jul '08

Hi All, From what I can see, bootstrap.py is there if you don't want either setuptools or zc.buildout to end up in your site-packages. Am I right? If so, where is it's use documented and what's the "correct" way to get hold of bootstrap.py? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 1

[zc.buildout] another way of specifying egg versions?
by Chris Withers 16 Jul '08

16 Jul '08

Just reading this: http://pypi.python.org/pypi/zc.buildout/1.0.6#automatic-buildout-updates Is this pattern: [buildout] zc.buildout-version == 1.0.6 setuptools-version == 0.6 ...only applicable to buildout and setuptools or does it generalize to: [buildout] <egg>-version <setup tools operators> <version text> ? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 2