Distutils-SIG March 2010

distutils-sig@python.org

72 participants
90 discussions

question about distribute installation and file permissions

by Darren Dale

I am looking through my site-packages directories, and it looks like Distribute installs *.py files with executable permissions. Is this necessary? Distutils does not do so. Nose, by default, will not run tests that live in executable modules. Thanks, Darren

11 years, 6 months

Re: [Distutils] Full egg name

by Martin Raspaud

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Forgot to cc the list... Tarek Ziadé skrev: > On Fri, Mar 26, 2010 at 2:04 PM, Martin Raspaud <martin.raspaud(a)smhi.se> wrote: > [..] >> What I want to do is to generate tarballs for our production servers (that have >> no compiling tools). > > I am not sure but, if you are planning to distribute a buildout for > you production server, what you could do is > zip a buildout you have built in a similar environment (==a binray > release of your buildout) > that contains all the eggs in eggs/ and possibly a download cache > within the buildout (download/) > > Then unzip in on your production server, and with the proper options > set in you cfg file, you can > make sure the server will not access pypi or anythong else, and use > the local cache and eggs, > > That's how I do (with some scripts located in collective.releaser), > and they are alternatives. Packaging an entire buildout environment is not really an option I think, since we have several projects using the same eggs, and we think it would be cleaner to share them (I'm thinking especially of big eggs, like scipy and numpy). On the other hand, I looked at collective.releaser and it is tempting. I will talk about this with my boss. >> The tarball should hold >> /myproject/myproject-0.3.0-py2.6-macosx-10.3-fat/<all files> >> in a compiled form (as would be the result of setup.py bdist) >> >> The info you gave me is usefull for locally developped packages that I can >> install as develop eggs. >> However some of them should be retreived from git, but I thought downloading >> them first, then put them as develop eggs. > > These packages are part of your buildout project or not ? If they > are, you can use a project like "mr.developer" to get those locally. Yes there are. I didn't know about mr.developer, looks nice, thanks ! As for git, I am using zerokspot.recipe.git to retrieve them as develop eggs. > But again, I am not sure about your release process and how these > packages are included in your environment so.. > > If you just want to create standalone binary distributions of single > python packages, I am not sure how buildout is related, and why you > are doing a recipe. Buildout is interesting to me because I can develop, test and use packages in a clean environment. I don't need to take care of any PYTHONPATH, all dependencies are installed automatically, and so on. So it is a great tool for development, and I got this from your book (which is really great by the way). As such I want to have a recipe for automatically creating packages to deploy on our servers. I see that it is indeed not buildout's philosophy build isolated eggs, but it is not the only thing I use it for :), it is a mere packaging tool for our production system I am building. Regards, Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLrMAtAAoJEBdvyODiyJI4cjoIAL7o1s7WjR0QSgEgQBSJXaxa 9nlQeFSx0y2ovK4fd3AX/m0FSj4KSf/yiJkG1BDoEPgeaptqUX2lzzp/0XdFbGDn 0t1eSoEL04Py+9eB8FJDzY42vozn54lPo/4cAa9wXW1WQQUJDNkJVh7nm+IYZWei 6PbPT3rY7ETAJAKHcREoAOtJcdrVeU9WhGwEF6nklzmsLNUaEB7kImBisCb/yNKa soEOXr7j5fc6D8ZCbiOyrtbsnrhcKC1EF+J+0e6bvVTftueCywON1fjULKlelyv1 y7KEPkbMr8o88EAluyW7V21NZ7qZDBkaUoVl8erE6hS8uHBODNzeL2KT0i66j88= =gjh8 -----END PGP SIGNATURE-----

11 years, 6 months

Re: [Distutils] How to use Nose plugins with buildout pbp.recipe.noserunner recipe ?

by Tarek Ziadé

On Fri, Mar 26, 2010 at 3:41 PM, Maxim Lacrima <lacrima.maxim(a)gmail.com> wrote: > Hello! > > It would be really nice if there was an option to set up plugins in > pbp.recipe.noserunner. > And of course there might be simpler way to enable plugins my solution, but > I can't figure out how to do this. I'll have a look sometimes. I think an argument in the command line (--with-PLUGIN_NAME) is enough, but I am not familiar with the code Regards Tarek -- Tarek Ziadé | http://ziade.org

11 years, 6 months

Full egg name

by Martin Raspaud

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am writing a recipe for buildout, and as such I would like to get the full name of a develop egg programatically as it would appear if I installed it. For example if the setup.py defines the name to "myproject", I would like to get myproject-0.3.0-py2.5-linux-x86_64.egg How to I get this ? I look a little bit in the setuptools source code, but it's not easy to find. Thanks, Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLrHDPAAoJEBdvyODiyJI4LhkH/0ep+wfUtAT7IzHdStNUcInT i9WQx9zyzMmIlWKzgHwSjtN48os3JfKE6iww6QHI6bNH6srDR+dSgeuytfEX8eeh oMuIYKR5LNgsrol1ZYulQHVz2UGdY308uI4rjxGSFhbwMEs3TGIX4VqrisHK/0uq RciBMtsa2cmuLrjeTVZVlLHnjGEpili7OUMcjiwcrNch0n24UtuS+hmGDx30E6bl rGIdr8rWDz7L5KwkbVu/tDAiqy7WRE4uQ8Voc/KDCLks4bXG6CjtcqC264hFqhYS XmYGqXkk32rJOV6NR2hqAfUapq7EaAVv50DJ2QopvxIiI5lpkxIkgcfbUFvH0aM= =KIh9 -----END PGP SIGNATURE-----

11 years, 6 months

How to use Nose plugins with buildout pbp.recipe.noserunner recipe ?

by Максим Lacrima

Hello! I've been using buildout. How can I install nose script with pbp.recipe.noserunner recipe (or anything else), so that I can pass an option to the script to enable plugin? Specifically, I want to enable nose plugin for GAE: bin/nose --with-gae. Thanks in advance. Sorry, if my English isn't proper. with regards, Maxim.

11 years, 6 months

log.py->logging ; trac for distutils2

by Zubin Mithra

Hi, While going through the distutils code base i realized that logging was performed with a "log.py" module similar to the logging module in stdlib. Apparently, it documented that the idea was to replace the current system using the "logging" module at some point, but it seems that it has`nt been done. I`ve made the necessary modifications and will upload to bitbucket tomorrow. I`ll also do the same for distutils so that maybe, its a backport for distutils? I had found that this was a pending task by looking through the code-base; and the task was quite trivial. I feel that it would be great if distutils2 had a "trac" of some sort where we could have tickets related to it. As distutils2 is not part of the python stdlib as of now, it would be inappropriate to have those tickets at bugs.python.org , i presume. Awaiting feedback, -- Zubin Mithra http://zubin71.wordpress.com

11 years, 6 months

Buildout documentation

by Baiju M

Hi All, I can see many people working with Buildout in this list. There are nearly 200 packages in PyPI with "Framework :: Buildout" category: http://pypi.python.org/pypi?:action=browse&c=512 This is really amazing. But the documentation for Buildout is not sufficient. I and few others created http://www.buildout.org during PyCON 2009. It would be great, if the users of Buildout coming forward to maintain that documentation. Now Buildout is used by Zope,Plone,Django and many other projects. May be someone can write an entire book about Buildout :) Regards, Baiju M

11 years, 6 months

Re: [Distutils] Help to create a setup.py (subdirectories aren't working)

by P.J. Eby

At 11:04 PM 3/24/2010 -0300, Hugo Doria wrote: >Hi guys, > >I am new to distutils and trying to create a setup.py for a project, >but i am having a problem. > >My project has this directory layout: > >/ >/AUTHORS >/README >/myproject (binary) >/MyProject >/MyProject/modules/ >/MyProject/modules/first.py >/MyProject/modules/__init__.py >/MyProject/output/ >/MyProject/output/second.py >/MyProject/output/__init__.py >/doc/manpage.1 > >Here's the setup.py that i did: > >from distutils.core import setup > >DATAFILES = [('/usr/share/man/man1', ['doc/manpage.1']), > >('/usr/share/doc/myproject',['AUTHORS','COPYING','README','TODO'])] > >setup(name='MyProject', > version='0.1', > license='GPL2', > description='Trying distutils, > author=['Hugo Doria'], > package_dir={'modules':MyProject/modules', > 'output':'MyProject/output'}, > packages=['modules', 'output'], > scripts=['myproject'], > data_files=DATAFILES) > >When i run setup.py install it does works. But i get this on my system: > >/usr//lib/python2.6/site-packages/modules >/usr//lib/python2.6/site-packages/output >/usr//lib/python2.6/site-packages/MyProject > >It's a bit strange, is not? It's exactly what you asked for. Your setup.py says you have two top-level packages called 'modules' and 'output', so that's what you got. >Shouldn't it be something like: > >/usr//lib/python2.6/site-packages/MyProject >/usr//lib/python2.6/site-packages/MyProject/output/ >/usr//lib/python2.6/site-packages/MyProject/modules/ > >What am i doing wrong? You're using a package_dir with more than one entry in it, which is a sign that your project's layout is broken. If you wanted a layout like the one you describe here, you need to: 1. Omit the package_dir option altogether 2. set packages = ['MyProject', 'MyProject.output', 'MyProject.modules'] 3. Add an __init__.py in the MyProject directory, to make it the parent package

11 years, 6 months

Releasing eggs as .tar.gz with setuptools or zc.buildout

by Martin Raspaud

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I am now working on a project that I need to deploy on different servers in a compiled form, as tar.gz files (the servers do not have gcc for example). The project comprises two libraries and an extra set of config files and scripts for batch computation. I would like to have a utility that does all the packaging for me, that is create a tar.gz for each lib and one for the scripts, each containing a directory with the compiled things. Here are my different approaches: - - setuptools bdist: This is almost what I need, except that it creates a usr dir on top of the tarball. - - zc.buildout: this looked promissing (although pretty hard to get into). I stumbled upon collective.releaser, which I thought was what I needed, but its project_deploy script just tarballs the entire buildout directory. Here is the config file I used for project_deploy: [buildout] parts = myproj [myproj] recipe=zerokspot.recipe.git repository=/data/proj/myproj branch=unstable as_egg=true I am getting quite desperate... Can anyone give me pointers ? Thanks, Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLqjFQAAoJEBdvyODiyJI4Y/cH/0/3osiqHWlzoT4lDiSgnrSu oG/mQMUHE+kOVHzDaZlf6mEQiTw0Ro2JPOwSSYlmf7dMXxmcCjkvNSmaqf2iYNE6 DN2SfMguIYG7v+hU3y9D9nPCdg4uf0kpxvTOFqm4cGkhnsqnIsy585eW6NLuXiwU pDuWlkLmYcFgVZGLczEJQ+p0h9ujigrVUZfH1vq+hn1r+Fpa7X69N2EMtBxq/Ull svqHQrNrEI3Brcv/9T/JMgen3//Mgb4vUrbN81LBa6rOJYth6AK6dBbkp5wicaUn QnPrl5/im59UJ5IT5Mrbj7o4kYdvKaxM9Iw+5fX4rnp0nV8mlbKv5vastCCJtp0= =qqAr -----END PGP SIGNATURE-----

11 years, 6 months

Help to create a setup.py (subdirectories aren't working)

by Hugo Doria

Hi guys, I am new to distutils and trying to create a setup.py for a project, but i am having a problem. My project has this directory layout: / /AUTHORS /README /myproject (binary) /MyProject /MyProject/modules/ /MyProject/modules/first.py /MyProject/modules/__init__.py /MyProject/output/ /MyProject/output/second.py /MyProject/output/__init__.py /doc/manpage.1 Here's the setup.py that i did: from distutils.core import setup DATAFILES = [('/usr/share/man/man1', ['doc/manpage.1']), ('/usr/share/doc/myproject',['AUTHORS','COPYING','README','TODO'])] setup(name='MyProject', version='0.1', license='GPL2', description='Trying distutils, author=['Hugo Doria'], package_dir={'modules':MyProject/modules', 'output':'MyProject/output'}, packages=['modules', 'output'], scripts=['myproject'], data_files=DATAFILES) When i run setup.py install it does works. But i get this on my system: /usr//lib/python2.6/site-packages/modules /usr//lib/python2.6/site-packages/output /usr//lib/python2.6/site-packages/MyProject It's a bit strange, is not? Shouldn't it be something like: /usr//lib/python2.6/site-packages/MyProject /usr//lib/python2.6/site-packages/MyProject/output/ /usr//lib/python2.6/site-packages/MyProject/modules/ What am i doing wrong? Thanks. -- Hugo

11 years, 6 months

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

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