I am maintaining a package that includes several scripts, and I recently
added a man page. Unfortunately, I was unable to figure out how to
specify the man page with setuptools. I ended up switching back to
vanilla distutils, which allowed me to specify the man page in setup.py:
Is there an equivalent way to do this with setuptools? The closest
thing I could find in the setuptools documentation was, "Note, by the
way, that this encapsulation of data files means that you can't actually
install data files to some arbitrary location on a user's machine; this
is a feature, not a bug." I appreciate the well-intended thought, but I
can't find any feature for specifying man pages. I don't want to
install to an arbitrary location, but I need to be able to install to
Is there a way to do this with setuptools, or do I need to keep using
distutils? I would love to be able to use the "console_scripts"
feature, so it would be great if I could use setuptools, but obviously
the man pages are higher priority. I feel like I must be missing
something obvious. Thanks.
PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868
A quick question about this buildout option.
Am I right that it isn't actually enabled yet?
It doesn't seem to have any effect for me (this is on buildout 1.5.2),
but using -t has a noticeable effect.
Since about an hour or so, when I run ez_setup.py (by way of a
zc.buildout bootstrap.py script), I get this:
Traceback (most recent call last):
File "bootstrap.py", line 172, in <module>
File "<string>", line 76, in use_setuptools
File "<string>", line 70, in do_download
File "<string>", line 131, in download_setuptools
File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 126, in
return _opener.open(url, data, timeout)
File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 398, in open
response = meth(req, response)
File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 511, in
'http', request, response, code, msg, hdrs)
File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 436, in error
File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 370, in
result = func(*args)
File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 519, in
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 404: Not Found
And indeed, when I download ez_setup.py myself:
$ wget http://peak.telecommunity.com/dist/ez_setup.py
and run it, I also get the 404 on the URL:
I have been bootstrap.py-ing packages all day long and suddenly they
stopped to work. Am I doing something wrong, or is the ez_setup.py broken?
Kind regards, jw
New submission from Guy Rozendorn <guy(a)rzn.co.il>:
the cli should use SetConsoleCtrlHandler to ignore CTRL-C and pass it to its child process
title: cli.exe quits on ctrl-c, but python doesn't
Setuptools tracker <setuptools(a)bugs.python.org>
At 01:55 PM 1/20/2011 +0800, Pherl Liu wrote:
>Hmm, I think it now only delete pkg_resource when
>pkg_resrouces.VersionConflict is caught, but the fix should be also
>delete pkg_resources when pkg_resources.DistributionNotFound is caught.
Good catch. Under previous use cases, the only time you'd have
pkg_resources and *not* setuptools, it would be if you were bundling
pkg_resources. Nowadays, though, some distros split setuptools from
pkg_resources, so you can have an older, distro-supplied
pkg_resources, but no setuptools.
Anyway, I've fixed this in SVN and on the website now. Thanks!
At 03:40 PM 1/19/2011 +0800, Pherl Liu wrote:
>I think I can fix this by editing ez_setup.py
>adding oneline after pkg_resources.DistributionNotFound is caught,
>del pkg_resources, sys.modules['pkg_resources']
>Not sure if this makes sense.
That's already in current versions of ez_setup.py; 0.6c9 is several
years old. I'd suggest you use the svn externals to keep it up-to-date. See:
At 04:42 PM 1/12/2011 +0800, Pherl Liu wrote:
>I got some error messages when using ez_setup to download and use
>from ez_setup import use_setuptools
>from setuptools import setup
>setup(name = "blabla",
> test_suite = "some_test",
> namespace_package = ["some_namespace"],
> # many other options
>So I guess there might be some import problem in my machine (ubuntu
>lucid) that the pkg_resources.py cannot be loaded from the egg?
Try running this script in your project directory:
from ez_setup import use_setuptools
import sys, setuptools, pkg_resources
This should tell us what's going on with your "import problem" more
> From: Alexis Métaireau <alexis(a)notmyidea.org>
> On 12/21/2010 09:41 PM, Sridhar Ratnakumar wrote:
>> 3. Did anyone--Alexis and Tarek, in particular--think of real-world use
>> cases for virtual projects (and even "provides" in general) other than
>> the Zope transaction case? If yes, what are they?
> "Provides-Release" lists the specific projects provided with this
> distribution. One case I can think about is having a distribution
> providing two different projects.
> A software can have a project for the "core" features and a project for
> the "default-plugins". It can then provides the two projects in only one
> Those can be two virtual projects 'core' and 'defaultplugins', which can
> be *provided* by different projects then. This allows to choose between
> the possible projects when resolving the dependencies.
What is the benefit of distributing two projects in a single
distribution, compared to the more simpler (traditional) solution of
distributing them in separate distributions (and, optionally, making
one depend on another; eg: 'core' depend on 'defaultplugins')? Does
this benefit justify the cost of introducing a new metadata field?
> setuptools and distribute can be both provided by the same virtual project.
Is this the only real-world use of virtual projects? Are there
>> 4. Personally, I have needs for "virtual" packages from a binary (not
>> source) distribution perspective. For example, "MySQL-python" can be a
>> virtual package "provided by" the binary distributions: mysql5.1-python,
>> How would PEP 345's "Provides-Release" help, if at
>> all, in describing this scenario?
> I'm not sure it will help in this case, unfortunately.
I'm trying to automate my release process from vcs - something like:
run tests ->
fetch current major, minor from branch (e.g. release_1.2) and
revision from tag (e.g. v1.2.1) ->
upload with current major, minor and revision +1 >
tag with such current major, minor and incremented revision.
I'd like to set my version from outside my setup.py file, either via
setup.py or a commandline option - I don't want to execute code in my
setup.py since this usually causes all sort of headaches with missing
Is there any proper way to do it? Might I break other things unexpectedly?
contact me at public(a)[mysurname].eu
We are using extensively buildout to build ERP5 :
We are planning to extend buildout download API to provide a
packaging and caching system so that even if original source web site is down,
the buildout process can stil run. This could also be useful to build
Do you know of any similar project before we start?
This message was sent using IMP, the Internet Messaging Program.