Mailman 3 July 2008 - Distutils-SIG

A release to at least stop crashing on Subversion 1.5 would be nice
by Arlo Belshee 05 Aug '08

05 Aug '08

In command/sdist.py, line 90 refers to a global log function which does not exist. Thus, instead of logging a warning about not understanding Subversion, setuptools crashes. The default setup scripts for Pylons (and probably others) use svn revision tagging. Thus, the following causes a crash: easy_install Pylons paster create -t Pylons proj setup.py develop And, since the user hasn't done any config (or anything but follow a tutorial), he isn't able to easily figure out what went wrong. Also, since setuptools was likely installed automatically for him via the egg in the cheeseshop, he isn't aware of anything that may be in dev for setuptools. A new user's likely response is to get frustrated for 15 minutes, then move on to another web framework / language. Even if you don't provide svn 1.5 support, can you at least post an egg that won't crash in the presence of svn 1.5? Thanks. Arlo

4 3

upgrading buildout
by whit morriss 29 Jul '08

29 Jul '08

I'm perhaps running buildout in a bit of unusual fashion (from my virtual env bin rather than the builds bin) and updated it recently from 1.0.2 to 1.1.0 to debug some issue folks were having with fresh checkouts of one of my builds (see previous message). I was suprised when all my zc.recipe.cmmi deps were recompiled. not a huge deal due to the unusual circumstances, but seemed avoidable. I realize my upgrade is dependent on my virtualenv setup and was wondering if there is some standard way to upgrade a build's buildout version while avoiding unnecessary rebuilding. -w

2 3

[issue29] SVN detection for package indices breaks on Sourceforge.net
by Nathan R. Yergler 28 Jul '08

28 Jul '08

New submission from Nathan R. Yergler <nathan(a)yergler.net>: PackageIndex._download_html (setuptools/package_index.py) attempts to detect if an HTML page is a Subversion repository using the regular expression r'<title>Revision \d+:'. This breaks for Sourceforge subversion repositories, which include the project name before the "Revision" text (see http://cctools.svn.sourceforge.net/svnroot/cctools/vendorlibs/utidylib/ for an arbitrary example). ---------- messages: 64 nosy: nyergler priority: bug status: unread title: SVN detection for package indices breaks on Sourceforge.net _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue29> _______________________________________________

2 1

buildout directory computation change
by whit morriss 28 Jul '08

28 Jul '08

it looks like something changes in how some vars (ie buildout:egg-directory) gets computed between 1.0.2 and 1.1.0 OSError: [Errno 2] No such file or directory: '/Users/whit/dev/geo/alm3//Users/whit/dev/geo/alm3/develop-eggs' is the resulting error for: eggs-directory = ${buildout:directory}/develop-eggs instead of: '/Users/whit/dev/geo/alm3/develop-eggs' (which I believe works until at least 1.0.2) buildout seems to implicitly assume I want buildout:directory appended. is this a feature, bug, or something I can turn off? -w

3 6

[issue28] Error message is confusing if you accidentally try to instal a directory
by Ian Bicking 27 Jul '08

27 Jul '08

New submission from Ian Bicking <ianb(a)colorstudy.com>: I commonly encounter a problem where a person creates a directory with a name, then tries to install a package with the same name as the directory. easy_install then things they were referring to the directory name. For instance: $ mkdir Pylons $ mkdir Pylons/src/MyProject # etc... $ easy_install Pylons Processing Pylons error: couldn't find a setup script in Pylons I think the error message could just be changed, first to make sure the directory ends with os.path.sep and then saying "error: couldn't find a setup script in the directory Pylons/" -- with that error message most people would figure out the problem quickly. ---------- messages: 63 nosy: ianb(a)colorstudy.com priority: bug status: unread title: Error message is confusing if you accidentally try to instal a directory _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue28> _______________________________________________

1 0

how to get pypi-equivalent rendering of long_description?
by Chris Withers 26 Jul '08

26 Jul '08

Hi All, I was to check how my long_description will show on pypi before I upload the egg. What's the best way do this? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

5 10

[zc.buildout] building a testrunner
by Chris Withers 25 Jul '08

25 Jul '08

Hi All, I've just finished making one of my python libraries into something that setuptools is happy with: https://secure.simplistix.co.uk/svn/Simplistix/twiddler/trunk/ I'm trying to add a short buildout.cfg next to the setup.py so I can check this project out, run bootstrap.py, run buildout and then do: C:\LocalSVN\twiddler> bin\test ...to run the tests. Here's the buildout.cfg I currently have: [buildout] develop = . parts = test [test] recipe = zc.recipe.testrunner eggs = twiddler Now, if I do: C:\LocalSVN\twiddler> bin\test -m twiddler ...I get the results I'd expect. However, if I do: C:\LocalSVN\twiddler> bin\test I get the following unexpected output: Test-module import failures: Module: eggs.setuptools-0.6c5-py2.4.egg.setuptools.tests.test_resources ImportError: No module named eggs.setuptools-0.6c5-py2.4.egg.setuptools.tests.te st_resources Module: eggs.setuptools-0.6c8-py2.4.egg.setuptools.tests.test_packageindex ImportError: No module named eggs.setuptools-0.6c8-py2.4.egg.setuptools.tests.te st_packageindex Module: eggs.setuptools-0.6c8-py2.4.egg.setuptools.tests.test_resources ImportError: No module named eggs.setuptools-0.6c8-py2.4.egg.setuptools.tests.te st_resources Module: eggs.zc.buildout-1.0.7_dev-py2.4.egg.zc.buildout.tests ImportError: No module named eggs.zc.buildout-1.0.7_dev-py2.4.egg.zc.buildout.te sts Module: eggs.zc.buildout-1.1.0-py2.4.egg.zc.buildout.tests ImportError: No module named eggs.zc.buildout-1.1.0-py2.4.egg.zc.buildout.tests Module: eggs.zc.recipe.egg-1.1.0-py2.4.egg.zc.recipe.egg.tests ImportError: No module named eggs.zc.recipe.egg-1.1.0-py2.4.egg.zc.recipe.egg.te sts Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.common.tests.te st_idatetime ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.common.tests.test_idatetime Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.common.tests.te st_import_interfaces ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.common.tests.test_import_interfaces Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_adap ter ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.tests.test_adapter Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_advi ce ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.tests.test_advice Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_decl arations ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.tests.test_declarations Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_docu ment ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.tests.test_document Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_elem ent ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.tests.test_element Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_inte rface ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.tests.test_interface Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_odd_ declarations ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.tests.test_odd_declarations Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_sort ing ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.tests.test_sorting Module: eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_veri fy ImportError: No module named eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.inte rface.tests.test_verify Module: eggs.zope.testing-3.6.0-py2.4.egg.zope.testing.tests ImportError: No module named eggs.zope.testing-3.6.0-py2.4.egg.zope.testing.test s Module: eggs.zope.testing-3.6.0-py2.4.egg.zope.testing.testrunner.tests ImportError: No module named eggs.zope.testing-3.6.0-py2.4.egg.zope.testing.test runner.tests Running zope.testing.testrunner.layer.UnitTests tests: Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds. <snip expected output> Test-modules with import problems: eggs.setuptools-0.6c5-py2.4.egg.setuptools.tests.test_resources eggs.setuptools-0.6c8-py2.4.egg.setuptools.tests.test_packageindex eggs.setuptools-0.6c8-py2.4.egg.setuptools.tests.test_resources eggs.zc.buildout-1.0.7_dev-py2.4.egg.zc.buildout.tests eggs.zc.buildout-1.1.0-py2.4.egg.zc.buildout.tests eggs.zc.recipe.egg-1.1.0-py2.4.egg.zc.recipe.egg.tests eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.common.tests.test_ida tetime eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.common.tests.test_imp ort_interfaces eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_adapter eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_advice eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_declaratio ns eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_document eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_element eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_interface eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_odd_declar ations eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_sorting eggs.zope.interface-3.4.1-py2.4-win32.egg.zope.interface.tests.test_verify eggs.zope.testing-3.6.0-py2.4.egg.zope.testing.tests eggs.zope.testing-3.6.0-py2.4.egg.zope.testing.testrunner.tests How come? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

3 7

zc.buildout poll
by Tarek Ziadé 24 Jul '08

24 Jul '08

Hi, I have an OSCON talk tomorrow about zc.buildout and I am trying to see if it's used outside the Zope community, for public projects I can show as examples on a slide If you do so, please let me know ! Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/

2 1

`develop' doesn't appends my package's directory to sys.path
by Gustavo Narea 20 Jul '08

20 Jul '08

Hello, everyone. I have an script which is supposed to run my test suite periodically, and the routine is basically this: 1.- It checkouts my app's source from the repository, and stores it in a different directory on every checkout. 2.- It runs setuptools build. 3.- It runs setuptools develop. 4.- It runs my test suite (via setuptools unittest). But setuptools' develop doesn't append my project's path to sys.path; I don't know what is going on, but I'm absolutely sure about that. Here is part of the verbose output of the script (it's actually not an script per se; I'm using an Ant like app, part of the Bitten continuous integration system): > [DEBUG ] Executing <function exec_ at 0x83ccdf4> with arguments: > {'executable': './setup.py', 'args': 'develop'} > [DEBUG ] Executing ['./setup.py', 'develop'] And because my package is not accessible, its modules are not accessible either: > ImportError: No module named build.lib.animador.config Then, from the Python interpreter, I check sys.path and I find that my package's path is not included. But if I manually run `setup.py develop', and then open the Python interpreter again, the path is included. Here's the output of my script http://paste.turbogears.org/paste/3255 and here's the full output of `setup.py develop' http://paste.turbogears.org/paste/3256 Also, 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 I hope someone can help me out; I have spent days trying to fix this. Thanks in advance. -- Gustavo Narea. General Secretary. GNU/Linux Matters. http://www.gnulinuxmatters.org/

4 7

Distutils for CygWin pyffmpeg
by Darthcoder 20 Jul '08

20 Jul '08

During the build of pyFFMpeg.py etc under CygWin/msys following error occurs File "F:\Python25\lib\distutils\version.py", line 107, in parse raise ValueError, "invalid version number '%s'" % vstring ValueError: invalid version number '2.18.50.20080109' According to the forums this is some sort of bug inside distutils... One recommendations is to use version 1.37. instead of current 1.38 cause that uses unixcompiler.py instead of cygwincompiler.py,... how does one to this? -- View this message in context: http://www.nabble.com/Distutils-for-CygWin-pyffmpeg-tp18552019p18552019.html Sent from the Python - distutils-sig mailing list archive at Nabble.com.

1 0