Distutils-SIG March 2010

distutils-sig@python.org

72 participants
90 discussions

[buildout] Impossible to install develop eggs
by Saint Germain 20 Mar '10

20 Mar '10

Hello, I'm trying to use buildout with develop eggs, but it seems that they cannot be installed. Here is the scenario : 1) I create a simple project in /home/user/project mkdir mymodule touch mymodule/__init__.py echo -e "from setuptools import setup\nPACKAGE = 'mymodule'\nVERSION = '0.1'\nsetup(name=PACKAGE, version=VERSION, packages=['mymodule'] )" > setup.py 2) I use the following buildout.cfg [buildout] develop = /home/af79141/project parts = eggs [eggs] recipe = zc.recipe.egg eggs = mymodule 3) I copy bootstrap.py in the directory ( http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py) 4) python bootstrap.py 5) bin/buildout I end up with the following content: bin bootstrap.py buildout.cfg develop-eggs eggs parts No lib/python/site-packages are created ! But there is a file mymodule.egg-link in develop-eggs with the following content: /home/users/project . What am I doing wrong ? I was expecting a created file like lib/python/site-packages/mymodule ? Thanks in advance,

4 5

setuptools data_files and bdist_egg
by Alain Leufroy 20 Mar '10

20 Mar '10

I'm a setuptools user and I appreciate it a lot, particularly for the automatic dependency installation and eggs. I found over the web that one of egg features is that files shouldn't be strewn all over the disk. However is there a way to put files outside the egg install directory (e.g. /usr/share/doc) ? The data_file list given as an argument to the setup method allows to specify where data files should be installed. But when I try to install a distribution using easy_install with an .egg file, all data files are copied in the egg install directory. This means that the prefix for relative path specified in the data_file list is the egg install directory instead of <sys.prefix>. Is there a way to force easy_install to use <sys.prefix> as the prefix for relative data file paths ? Best regards -- Alain Leufroy

2 2

Re: [Distutils] repeatable and updatable virtualenv
by Saint Germain 19 Mar '10

19 Mar '10

2010/3/19 Brad Allen <bradallen137(a)gmail.com>: > On Fri, Mar 19, 2010 at 10:23 AM, Saint Germain <saintger(a)gmail.com> wrote: >> >> 2010/3/19 Brad Allen <bradallen137(a)gmail.com> >>> >>> On Tue, Mar 16, 2010 at 2:26 AM, Chris Withers <chris(a)simplistix.co.uk> >>> wrote: >>> > Hi All, >>> > >>> > How can I set up a virtualenv in such a way that I can version control >>> > the >>> > packages and their versions that are installed in it? >>> > >>> > The answer would appear to a custom bootstrap script, but how would I >>> > think >>> > update an existing virtualenv when I added or removed packages or >>> > changed >>> > the version of a specific package? >>> >>> >>> You could try envbuilder; I find it very helpful for setting up >>> development environments repeatably when developing several related >>> packages ('er, 'module distributions') simultaneously. >>> >>> It basically just creates a virtualenv, checks out/clones whatever you >>> specify in the .env confiig file, and runs setup.py develop on each of >>> the checked out packages into the virtualenv. Also, it provides a way >>> to apply commands across all the checked out packages (like 'update' >>> or 'status') >>> >>> http://pypi.python.org/pypi/envbuilder/0.1.4 >>> >>> I think a similar functionality can be had using buildout with >>> mr.developer, but I have not tried it yet. However as far as I know, >>> buildout does not create a virtualenv (yet). >>> >> >> I'm currently trying more or less the same thing by combining buildout with >> virtualenv and pip. >> So far it's working without problem except the installation of develop eggs >> (see my other message). >> >> Buildout can create virtualenv without problem (see >> http://pypi.python.org/pypi/rjm.recipe.venv/0.7) and can use pip to install >> editable package (see http://pypi.python.org/pypi/gp.recipe.pip) under >> version control (CVS, SVN, Mercurial...) > > Thanks for the tip! > > >> Now if only I can solve the develop eggs issue, I would be very happy ! > > What is that issue? > See here: http://mail.python.org/pipermail/distutils-sig/2010-March/015729.html I think that it's not a bug or a missing functionality but it's just that I haven't fully understand the whole thing about develop eggs. The eggs are correctly generated but I haven't managed to install them automatically. Anyway after it is solved, I can confirm that buildout + distribute + virtualenv + pip is a very powerful combination ! Don't hesitate to ask questions if you want to use the same approach. There are some points which are still rough and I need to send some patch upstreams. But mainly it works (and rocks). Regards,

1 0

distutils: upload fails if maintainer name is unicode
by Sébastien Barthélemy 18 Mar '10

18 Mar '10

Hello, when I run "python setup.py sdist upload" on my package, it fails with the following traceback: Traceback (most recent call last): File "setup.py", line 86, in <module> cmdclass=cmdclass) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/distutils/core.py", line 152, in setup dist.run_commands() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/distutils/dist.py", line 987, in run_commands self.run_command(cmd) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/distutils/dist.py", line 1007, in run_command cmd_obj.run() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/distutils/command/upload.py", line 57, in run self.upload_file(command, pyversion, filename) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/distutils/command/upload.py", line 135, in upload_file value = str(value) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 1: ordinal not in range(128) I'm running Python 2.6.4 on mac os X. Note also that I could register the package on pypi without any problem. Apparently, the problem occurs because of the maintainer=u'Sébastien BARTHÉLEMY' argument to the setup command. This seems to be a known problem : http://bugs.python.org/issue1076233 http://stackoverflow.com/questions/1162338/whats-the-right-way-to-use-unico… If I read well, it should be fixed in 2.6. Can you confirm this problem is (at least officially) fixed for python 2.6.4 ? Any idea or workaround ? Thanks Sébastien

2 3

disutils2 and python 2.4
by Nicholas Bower 18 Mar '10

18 Mar '10

I joined the list after this discussion: http://mail.python.org/pipermail/distutils-sig/2010-March/015607.html and want to point out that even the most recent versions of Zope 2.x for example still recommend Python 2.4. http://www.zope.org/Products/Zope/2.11.4/Zope-2-11-4-released In other words, there are probably alot of web apps out there (eg think about sites on Plone CMS) potentially running Python 2.4. I run a dedicated Python 2.4 just for Plone for example (the buildout of which is based on virtualenv and setuptools anyway I guess). Whether distutils2 would be used by these projects of course is another matter. Just pointing out Python 2.4 is absolutely not unimportant.

3 2

[buildout] pythonpath
by John Griessen 18 Mar '10

18 Mar '10

I've got a buildout config partially working, but missing ability to find some views. How would you add paths to find cottagematic_bld/cottagematic_com/polls and /home/john/djangotemplates to this buildout config? --------------------------------- [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 [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 urls = http://code.google.com/p/django-messages/source/browse/#svn/branches/messag… wsgi = true eggs = ${buildout:eggs} project = cottagematic_com ------------------------------------------------- The django app has info to find things, but somehow the python path doesn't get all of it. From django settings.py: INSTALLED_APPS = ( 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.admin', ) TEMPLATE_LOADERS = ( 'django.template.loaders.filesystem.load_template_source', 'django.template.loaders.app_directories.load_template_source', ) TEMPLATE_DIRS = ( os.path.join(os.path.dirname(__file__), "templates"), "/home/john/djangotemplates" thanks, John

2 3

buildout / distribute issue
by Kent Tenney 18 Mar '10

18 Mar '10

I'm abusing buildout thusly: $ mkdir bo $ cd bo $ wget http://python-distribute.org/bootstrap.py buildout.cfg: ---------------------------- [buildout] parts = interp [interp] recipe = zc.recipe.egg interpreter = py eggs = ---------------------------- $ python bootstrap.py -d $ bin/buildout Installing interp. Installing . Generated interpreter '/tmp/bo/bin/py'. $ bin/py File "bin/py", line 6 , ^ SyntaxError: invalid syntax from bin/py: ----------------------------------- sys.path[0:0] = [ , ] ----------------------------------- Thanks, Kent

2 1

Re: [Distutils] setuptools dependencies failure and wildcards
by P.J. Eby 17 Mar '10

17 Mar '10

At 09:16 PM 3/14/2010 +1100, Nicholas Bower wrote: >I have the following simple dependencies using setuptools; > > install_requires=['shapely==1.0.14','sqlalchemy==0.5.8'], > >Two questions; > >1) Shapely will not work. The available packages are; > >Shapely-1.0.14.win32.py24.exe (md5). >Shapely-1.0.14.win32.py25.exe (md5). >Shapely-1.0.14.win32.py26.exe (md5). > >but python version is not being appended as below. Is shapely thus >incompatible with setuptools? No; the problem is that there's a broken link on the Shapely home page at http://trac.gispython.org/lab/wiki/Shapely - it links to a non-existent .exe file in this line: "Windows users should use the executable <http://pypi.python.org/packages/2.5/S/Shapely/Shapely-1.0.14.win32.exe#md5=…> installer, which contains the required GEOS DLL" easy_install is seeing this link and thinks it's preferable, due to the way it sorts candidate URLs, and it isn't smart enough (yet) to backtrack on broken links. You can work around this by adding 'dependency_links=[]' to your setup(), replacing the [] with a list of specific links to the individual .exe files; this will keep easy_install from ever reading the PyPI page or wiki page with the broken link. Of course, you should also suggest the shapely maintainers fix the broken link, since it is broken for humans as well as for easy_install. ;-) >2) How does one say "the latest release of sqlalchemy 0.5.x". >Unfortunately <0.6 picks up 0.6beta and I can see no way to do >wildcards in the docs and just say "give me the latest 0.5 series". <0.6dev will do the trick.

3 5

mr.developer questions
by John Griessen 17 Mar '10

17 Mar '10

I made a buildout including mr.developer, changed some of my django app files such as urls.py, reran buildout and changes gone, so I misunderstood. What is the VCS underlying mr.developer, SVN?, and how to you tell it to add files and commit via mr.developer? John

2 1

distribute_setup.use_setuptools: what if I want to keep the existing old setuptools?
by Sridhar Ratnakumar 16 Mar '10

16 Mar '10

Tarek, For some background on this, see http://bitbucket.org/srid/modern-package-template/issue/9/distribute_setup-… The intent behind calling distribute_setup.use_setuptools (and ez_setup.use_setuptools) is that if the user does not have setuptools installed, running "python setup.py install" will automatically install it for him. But if the user already has setuptools, running distribute_setup.use_setuptools upgrades that installation to Distribute. This goes against the original intention, correct? Is it reasonable to provide an option to `use_setuptools` that would decide if Distribute must replace the existing setuptools or not? -srid

1 1

← Newer
1
2
3
4
5
6
7
8
9
Older →

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 March 2010