Mailman 3 September 2009 - Distutils-SIG

Re: [Distutils] setup.cfg new format proposal
by P.J. Eby 12 Sep '09

12 Sep '09

At 12:28 AM 9/12/2009 +0200, Tarek Ziadé wrote: >On Fri, Sep 11, 2009 at 7:40 PM, Jim Fulton <jim(a)zope.com> wrote: > > > >> The second motivation is : why do I need to run some code to get the > >> metadata fields ? > > > > Turning the config file into code means you'd be running code. :) > >Well that's very different. You will be running a function that is >provided in the stdlib, >in a vanilla Python, and that will be restricted to string comparisons >basically. > >In other words, it is more likely to be a translation of setup.cfg >into a "localized" >setup.cfg. But in that case, why not just have a 100% static format without any dynamic content whatsoever, and run a "configure.py" or some such (perhaps "distconfig.py") to generate it? Since it's not setup.py, there are no backward compatibility issues, and we can actually get the full benefit of environment-specific configuration (e.g. library locations, etc.).

2 1

Distribute 0.6.1 released
by Tarek Ziadé 11 Sep '09

11 Sep '09

Hello I am happy to announce the release of Distribute 0.6.1. Changes: * zip_ok is now True by default. * package_index.urlopen now catches BadStatusLine and malformed url errors. * Fixed invalid URL error catching. * Fixed invalid bootstraping with easy_install installation. Thanks to Florian Shchulze for the help * Removed buildout/bootstrap.py. A new repository at bitbucket.org will create a specific bootstrap.py script. * The bootstrap process leave setuptools alone if detected in the system and --root, --user or --prefix is provided, but is not in the same location. The next release of the 0.6 series will try to adress all remaining bugs in the tracker, The first 0.7 release is still under heavy work. Cheers Tarek -- Tarek Ziadé | http://ziade.org | オープンソースの岩！

5 8

distutils' sdist won't allow me to include a file called buildout.cfg in my source distribution
by Chris Withers 11 Sep '09

11 Sep '09

...which is kinda annoying :-( The problem is, in Python 2.6.2, line 357 of sdist.py. This ends up applying the following: exclude_pattern: applying regex r'^build\.*' ...which of course chomps buildout.cfg, with no possibility to add it back in MANIFEST.in :-( Where does the bug lie and should I submit a bug tracker issue? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

2 11

pkgutil.extend_path and .pkg files
by Thomas Heller 11 Sep '09

11 Sep '09

pkgutil is somehow connected to setuptools, so I assume this is the right place to ask this question. I'm exploring pkgutil.extend_path(), together with a pkg-file somewhere on my PYTHONPATH. I am wondering if it is somehow possible to interpret relative pathnames in the pkg-file relative to the directory which contains the pkg-file? -- Thanks, Thomas

3 2

Re: [Distutils] problem with http://nightly.ziade.org/distribute_setup.py
by Chris Withers 10 Sep '09

10 Sep '09

Tarek Ziadé wrote: > we have dropped the releases of egg format in 0.6.1 for various reasons, Huh? Where are these reasons documented? > and > the use_setuptools function cannot work anymore because it is exclusively using > binary eggs and their ability to be used in sys.path as-is with zero > installation. So much for drop-in compatibility with setuptools :-( > Florian Schulze and I started another repo to create a new bootstrap.py > that will bootstrap a zc.buildout environment using Distribute. > > http://bitbucket.org/tarek/buildout-distribute/ How about working on the buildout branch I'm working on rather than doing stuff separately all the time? Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

2 5

[buildout[ How do I use stuff specified in the distutils.command entry_point?
by Chris Withers 10 Sep '09

10 Sep '09

Hi All, Sphinx, among others, provides command in this entry point. With this buildout: [buildout] parts = sphinx [sphinx] recipe = zc.recipe.egg eggs = sphinx And based on the entry points listed here: http://bitbucket.org/birkenfeld/sphinx/src/447109cf9b01/setup.py#cl-182 I'd expect to be able to do: $ bin/buildout setup setup.py build_sphinx But I get: Running setup script 'setup.py'. usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'build_sphinx' Any ideas? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

2 4

virtualenv-distribute 1.3.4dev-1 released
by Florian Schulze 08 Sep '09

08 Sep '09

Hi! I'm happy to announce the release of virtualenv-distribute 1.3.4dev-1, which is a fork of virtualenv which uses distribute 0.6.1 instead of setuptools. Any feedback welcome. Regards, Florian Schulze

2 1

[buildout] trunk failures on Windows
by Chris Withers 08 Sep '09

08 Sep '09

Hi All, Thought I'd try and help Reinout van Rees out by running the tests on his branch on Windows, but found problems even when trying to run the tests on trunk: - running dev.py failed on Windows, I've fixed this in r103647 - Even so, running dev.py with Python 2.6 on Windows pops up a dialog box saying "The application failed to initialize properly (0xc0150004). Click OK to terminate the application". That said, the script still seems to run fine. This doesn't happen with Python 2.5 or 2.4. - There are test failures with Python 2.6 on Windows, I've attached the full run in windows.txt. cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk C:\LocalSVN\zc.buildout>bin\test.exe Running zope.testing.testrunner.layer.UnitTests tests: Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds. Failure in test c:\localsvn\zc.buildout\src\zc\buildout\buildout.txt Failed doctest test for buildout.txt File "c:\localsvn\zc.buildout\src\zc\buildout\buildout.txt", line 0 ---------------------------------------------------------------------- File "c:\localsvn\zc.buildout\src\zc\buildout\buildout.txt", line 452, in buildout.txt Failed example: print system(buildout), # doctest: +ELLIPSIS Expected: Develop: '/sample-buildout/recipes' Uninstalling data-dir. Installing data-dir. data-dir: Creating directory foo data-dir: Creating directory bin While: Installing data-dir. <BLANKLINE> An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): ... OSError: [Errno 17] File exists: '/sample-buildout/bin' Got: Develop: '/sample-buildout/recipes' Uninstalling data-dir. Installing data-dir. data-dir: Creating directory foo data-dir: Creating directory bin While: Installing data-dir. <BLANKLINE> An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 1659, in main getattr(buildout, command)(args) File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 532, in install installed_files = self[part]._call(recipe.install) File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 1203, in _call return f() File "/sample-buildout/recipes/mkdir.py", line 27, in install os.mkdir(path) OSError: [Error 183] Cannot create a file when that file already exists: '/sample-buildout/bin' ---------------------------------------------------------------------- File "c:\localsvn\zc.buildout\src\zc\buildout\buildout.txt", line 486, in buildout.txt Failed example: print system(buildout), # doctest: +ELLIPSIS Expected: Develop: '/sample-buildout/recipes' Installing data-dir. data-dir: Creating directory foo While: Installing data-dir. <BLANKLINE> An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): ... OSError: [Errno 17] File exists: '/sample-buildout/foo' Got: Develop: '/sample-buildout/recipes' Installing data-dir. data-dir: Creating directory foo While: Installing data-dir. <BLANKLINE> An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 1659, in main getattr(buildout, command)(args) File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 532, in install installed_files = self[part]._call(recipe.install) File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 1203, in _call return f() File "/sample-buildout/recipes/mkdir.py", line 27, in install os.mkdir(path) OSError: [Error 183] Cannot create a file when that file already exists: '/sample-buildout/foo' ---------------------------------------------------------------------- File "c:\localsvn\zc.buildout\src\zc\buildout\buildout.txt", line 562, in buildout.txt Failed example: print system(buildout), # doctest: +ELLIPSIS Expected: Develop: '/sample-buildout/recipes' Installing data-dir. data-dir: Creating directory foo data-dir: Creating directory bin While: Installing data-dir. <BLANKLINE> An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): ... OSError: [Errno 17] File exists: '/sample-buildout/bin' Got: Develop: '/sample-buildout/recipes' Installing data-dir. data-dir: Creating directory foo data-dir: Creating directory bin While: Installing data-dir. <BLANKLINE> An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 1659, in main getattr(buildout, command)(args) File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 532, in install installed_files = self[part]._call(recipe.install) File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 1203, in _call return f() File "/sample-buildout/recipes/mkdir.py", line 29, in install os.mkdir(path) OSError: [Error 183] Cannot create a file when that file already exists: '/sample-buildout/bin' ---------------------------------------------------------------------- File "c:\localsvn\zc.buildout\src\zc\buildout\buildout.txt", line 642, in buildout.txt Failed example: print system(buildout), # doctest: +ELLIPSIS Expected: Develop: '/sample-buildout/recipes' Installing data-dir. data-dir: Creating directory foo data-dir: Creating directory bin While: Installing data-dir. <BLANKLINE> An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): ... OSError: [Errno 17] File exists: '/sample-buildout/bin' Got: Develop: '/sample-buildout/recipes' Installing data-dir. data-dir: Creating directory foo data-dir: Creating directory bin While: Installing data-dir. <BLANKLINE> An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 1659, in main getattr(buildout, command)(args) File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 532, in install installed_files = self[part]._call(recipe.install) File "c:/localsvn/zc.buildout/src/zc/buildout/buildout.py", line 1203, in _call return f() File "/sample-buildout/recipes/mkdir.py", line 27, in install os.mkdir(path) OSError: [Error 183] Cannot create a file when that file already exists: '/sample-buildout/bin' unrecognized .svn/entries format in extdemo.c Creating library build\temp.win32-2.6\Release\extdemo.lib and object build\temp.win32-2.6\Release\extdemo.exp zip_safe flag not set; analyzing archive contents... extdemo.c Creating library build\temp.win32-2.6\Release\extdemo.lib and object build\temp.win32-2.6\Release\extdemo.exp zip_safe flag not set; analyzing archive contents... extdemo.c Creating library build\temp.win32-2.6\Release\extdemo.lib and object build\temp.win32-2.6\Release\extdemo.exp zip_safe flag not set; analyzing archive contents... extdemo.c Creating library build\temp.win32-2.6\Release\extdemo.lib and object build\temp.win32-2.6\Release\extdemo.exp extdemo.c Creating library build\temp.win32-2.6\Release\extdemo.lib and object build\temp.win32-2.6\Release\extdemo.exp zip_safe flag not set; analyzing archive contents... extdemo.c Creating library build\temp.win32-2.6\Release\extdemo.lib and object build\temp.win32-2.6\Release\extdemo.exp zip_safe flag not set; analyzing archive contents... extdemo.c Creating library build\temp.win32-2.6\Release\extdemo.lib and object build\temp.win32-2.6\Release\extdemo.exp zip_safe flag not set; analyzing archive contents... zip_safe flag not set; analyzing archive contents... extdemo.c Creating library build\temp.win32-2.6\Release\extdemo.lib and object build\temp.win32-2.6\Release\extdemo.exp zip_safe flag not set; analyzing archive contents... Ran 451 tests with 1 failures and 0 errors in 11 minutes 20.516 seconds. Tearing down left over layers: Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.

2 1

what does zc.recipe.egg do with disutils scripts?
by Chris Withers 08 Sep '09

08 Sep '09

Hi, I'm trying to get docutils installed and running with this part: [docs] recipe = zc.recipe.egg:scripts eggs = docutils However, the following scripts specified in docutils' setup.py are not installed: 'scripts' : ['tools/rst2html.py', 'tools/rst2s5.py', 'tools/rst2latex.py', 'tools/rst2newlatex.py', 'tools/rst2xml.py', 'tools/rst2pseudoxml.py', 'tools/rstpep2html.py', ],} How do I get them installed? I've tried adding dependent-scripts = true and/or interpreter = py, but nothing seems to work... What am I doing wrong? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

3 4

Distribute 0.6 released
by Tarek Ziadé 08 Sep '09

08 Sep '09

Hi all, I am pleased to announce the release of Distribute 0.6. Distribute is a friendly fork of the Setuptools project. You can get more info, download it and install it using the instructions from its PyPI page : http://pypi.python.org/pypi/distribute --- CHANGES (compared to setuptools 0.6c9) : setuptools * Packages required at build time where not fully present at install time. This closes http://bitbucket.org/tarek/distribute/issue/12. * Protected against failures in tarfile extraction. This closes http://bitbucket.org/tarek/distribute/issue/10. * Made Jython api_tests.txt doctest compatible. This closes http://bitbucket.org/tarek/distribute/issue/7. * sandbox.py replaced builtin type file with builtin function open. This closes http://bitbucket.org/tarek/distribute/issue/6. * Immediately close all file handles. This closes http://bitbucket.org/tarek/distribute/issue/3. * Added compatibility with Subversion 1.6. This references http://bitbucket.org/tarek/distribute/issue/1. pkg_resources * Avoid a call to /usr/bin/sw_vers on OSX and use the official platform API instead. Based on a patch from ronaldoussoren. This closes http://bitbucket.org/tarek/distribute/issue/5. * Fixed a SandboxViolation for mkdir that could occur in certain cases. This closes http://bitbucket.org/tarek/distribute/issue/13. * Allow to find_on_path on systems with tight permissions to fail gracefully. This closes http://bitbucket.org/tarek/distribute/issue/9. * Corrected inconsistency between documentation and code of add_entry. This closes http://bitbucket.org/tarek/distribute/issue/8. * Immediately close all file handles. This closes http://bitbucket.org/tarek/distribute/issue/3. easy_install * Immediately close all file handles. This closes http://bitbucket.org/tarek/distribute/issue/3. Cheers Tarek -- Tarek Ziadé | http://ziade.org

2 7