Distutils-SIG May 2010

distutils-sig@python.org

46 participants
72 discussions

using sub_commands in distutils
by Manlio Perillo 14 May '10

14 May '10

Hi. In a package, I have gettext catalog messages, and I want to compile them when the package is build. I looked at the Mercurial setup.py script, and what it does is: from distutils.command.build import build build.sub_commands.insert(0, ('build_mo', None)) Is this the correct way? Thanks Manlio

4 8

[buildout] ${} substitutions don't happen in buildout:extends?
by Chris Withers 12 May '10

12 May '10

Hi All, Here's the scenario; we have per-project buildouts, but where and how people lay out their checkouts and how they access svn (svn:// versus http:// versus https:// externally). Buildout lends itself to this flexibility by having the per-project buildouts use templated values, with those values being specified in ~/.buildout/default.cfg ...except, this doesn't seem to work for buildout:extends. For example, here's a project buildout: [buildout] extends = ${buildout:base_location}/versions/repoze.bfg-1.2-versions.cfg ... And here's what's in ~/.buildout/default.cfg: [buildout] base_location = /Users/chris/LocalSVN/base ...but, the normal ${} substitution doesn't appear to happen in the extends line, so I get the following error: IOError: [Errno 2] No such file or directory: '/Users/chris.withers/LocalSVN/demoapp/${buildout:base_location}/versions/repoze.bfg-1.2-versions.cfg' What am I doing wrong? How can I achieve my aims with buildout 1.4.3 or later? cheers, Chris

2 2

distribute and install --root
by Nikolaus Rath 11 May '10

11 May '10

Hello, How can I convince distribute to install a module in a different root directory, without also switching to the ~/.local/ scheme? I was surprised to find that the following doesn't work: $ python setup.py install --single-version-externally-managed --root staging/ running install running build running build_py creating build creating build/lib.linux-i686-2.6 creating build/lib.linux-i686-2.6/mymodule copying mymodule/mymodule.py -> build/lib.linux-i686-2.6/mymodule copying mymodule/__init__.py -> build/lib.linux-i686-2.6/mymodule running install_lib creating staging creating staging/home creating staging/home/nikratio creating staging/home/nikratio/.local creating staging/home/nikratio/.local/lib creating staging/home/nikratio/.local/lib/python2.6 creating staging/home/nikratio/.local/lib/python2.6/site-packages creating staging/home/nikratio/.local/lib/python2.6/site-packages/mymodule copying build/lib.linux-i686-2.6/mymodule/mymodule.py -> staging/home/nikratio/.local/lib/python2.6/site-packages/mymodule copying build/lib.linux-i686-2.6/mymodule/__init__.py -> staging/home/nikratio/.local/lib/python2.6/site-packages/mymodule [...] I want mymodule to end up somewhere in staging/usr/lib/*. Thanks, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C

3 7

How to track performance improvements in my code?
by Matthew Wilson 10 May '10

10 May '10

I know how to use timeit and/or profile to measure the current run-time cost of some code. I want to record the time used by some original implementation, then after I rewrite it, I want to find out if I made stuff faster or slower, and by how much. Other than me writing down numbers on a piece of paper on my desk, does some tool that does this already exist? If it doesn't exist, how should I build it? Matt

3 3

inability to pass setup.py command line arguments to dependency setups
by Kent 10 May '10

10 May '10

Consider the case where you want your setup to install third-party software, but you want/need to pass an argument to the command line that runs "python setup.py --argument install" or "python setup.py -- argument bdist_egg" As far as I could research, this feature is unavailable. If there is a graceful way to accomplish this I would really like to know. If there is no way, I offer a workaround to those who require this functionality. Consider a setup.py with the following setup() function call: ________________________________________________________________________________________ setup( name='pylotengine', version='0.1', description='', author='', author_email='', install_requires=[ "SQLAlchemy >= 0.6", "tg.devtools >= 2.0.1", ... ... ) ________________________________________________________________________________________ Now, when SQLAlchemy is to be installed, there is a really nice feature that can be enabled to build it with C extensions for performance, so you want easy_install to run: "python setup.py --with-cextensions bdist_egg" instead of just: "python setup.py bdist_egg" In order to pass the "--with-cextensions" argument, I do the following (again, not a very graceful solution): ________________________________________________________________________________________ # -*- coding: utf-8 -*- try: from setuptools import setup, find_packages except ImportError: from ez_setup import use_setuptools use_setuptools() from setuptools import setup, find_packages #kb: since apparently setuptools has no mechanism to pass # arguments to the dependencies, I am "decorating" the function # that runs the command and adding the arguments myself... from setuptools.command.easy_install import easy_install normal_run_setup_fn = easy_install.run_setup def setup_hook(self, setup_script, setup_base, args): # SQLAlchemy we want to run setup.py --with-cextensions if setup_script.find('/SQLAlchemy') > -1 and setup_script.endswith('setup.py'): args.insert(0,'--with-cextensions') normal_run_setup_fn(self, setup_script, setup_base, args) easy_install.run_setup = setup_hook setup( name='pylotengine', version='0.1', description='', author='', author_email='', #url='', install_requires=[ #kb start "SQLAlchemy >= 0.6", "tg.devtools >= 2.0.1", "psycopg2 >= 2.0.11", ... ...rest of setup() call... ________________________________________________________________________________________ Hope this is helpful to someone...

7 10

Re: [Distutils] ..\setup.py relative invocation (was: [issue108] develop install fails if path to setup.py is relative)
by P.J. Eby 10 May '10

10 May '10

At 03:21 PM 5/9/2010 +0300, anatoly techtonik wrote: >setup.py fails miserably when invoked using relative path, i.e. >`python ../../setup.py ...`. In this case it attempts to look up >referenced files in current directory - not in its own dir. > >What is it needed for? The distutils were simply written with the assumption that that's how things are... and there were never any tests that did otherwise. As a result, there's lots of code that simply operates on relative paths, beginning from the relative paths that are provided by setup(). >Does distutils2 fix this? > >I ask, because it adds another "save cwd;cd;...;restore cwd" yak >shaving wrapper to development process, and the error message for >failure is not very intuitive. FWIW, you can always use "easy_install path/to/directory", if you're just going to be running an install. I don't know if pip will wrap in this way, but it seems to me there was also a buildutils or some such package floating around a few years ago that included a simple command for running setup scripts with different interpreters, in any directory, etc.

3 2

easy_install (and hence virtual_env, buildout, etc) versus .msi
by Chris Withers 10 May '10

10 May '10

Hi All, Is there any way to get easy_install to use .msi's as a source for distros on Windows? Twisted is only distributed as a .msi :-/ Chris

1 0

..\setup.py relative invocation (was: [issue108] develop install fails if path to setup.py is relative)
by anatoly techtonik 09 May '10

09 May '10

setup.py fails miserably when invoked using relative path, i.e. `python ../../setup.py ...`. In this case it attempts to look up referenced files in current directory - not in its own dir. What is it needed for? Does distutils2 fix this? I ask, because it adds another "save cwd;cd;...;restore cwd" yak shaving wrapper to development process, and the error message for failure is not very intuitive. -- anatoly t. On Sat, May 8, 2010 at 10:26 PM, P.J. Eby <pje(a)telecommunity.com> wrote: > At 12:23 PM 5/8/2010 +0000, techtonik wrote: > >> New submission from techtonik <techtonik(a)gmail.com>: >> >> (stable011) M:\p\python\trac\env\stable011>python >> ..\..\bitten\bitten-0.6.x\setup.py develop -mxd testenv\plugins > > Just FYI: you can NEVER run a setup.py in a different directory than the one > where you're located, whether it's with distutils or setuptools. > > I have no idea whether it works with distutils2 or is intended to be > supported, but if it's based on disutils code, then you MUST change to the > correct directory before running it. > >

2 1

Re: [Distutils] [issue108] develop install fails if path to setup.py is relative
by P.J. Eby 08 May '10

08 May '10

At 12:23 PM 5/8/2010 +0000, techtonik wrote: >New submission from techtonik <techtonik(a)gmail.com>: > >(stable011) M:\p\python\trac\env\stable011>python >..\..\bitten\bitten-0.6.x\setup.py develop -mxd testenv\plugins Just FYI: you can NEVER run a setup.py in a different directory than the one where you're located, whether it's with distutils or setuptools. I have no idea whether it works with distutils2 or is intended to be supported, but if it's based on disutils code, then you MUST change to the correct directory before running it.

1 0

Does buildout have a way to issue its version of sys.path?
by kevin 08 May '10

08 May '10

Ok, I use vim in the console. I have python compiled into it, the system python. If i could get the value of sys.path in my buildout, I could add it to vim and then have omni completion for everything in the buildout. That's the goal. So: is there a way to get sys.path's value in a buildout? I'd like to make things a bit more automatic than copying the sys.path invocation in bin/buildout itself...

3 3

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Distutils-SIG May 2010