I recently installed Python 2.6.2 on MS Windows and would like to get
Easy Install/setuptools working. The associated download page
(http://pypi.python.org/pypi/setuptools) provides MS Windows .EXE
installers for Python versions 2.3 - 2.5 only. Are there any prospects
for a 2.6 installer? Or is there another reasonably straightforward way
to get Easy Install/setuptools built and installed?
We have a suite of tools in the 'lazr' namespace that we've begun to
release as open source. All of these packages are maintained under
bzr and it's really nice to be able to add this to our setup.py:
This extends setuptools so that we can use bzr instead of the built-in
revision control systems. With that, 'python setup.py sdist' pulls in
the right stuff. All of our packages are buildout based.
The problem is that when we buildout the package, the download cache
is never consulted and setuptools_bzr is /always/ downloaded. This is
a non-starter for our production environments, which are not allowed
to hit the external 'net during build time. Because of this, we've
had to disable the setup_requires. We can kind of make things work
with MANIFEST.ins but I'd prefer to be able to use setup_requires.
Otherwise, um, what's the point of having this plugin?
I'm not sure whether this is a bug in setuptools, distutils, or
buildout, but since y'all are here, we should be able to figure it
out. Or do you not think this is a bug?
If you agree it's a bug, and we can agree where it's a bug, I'd be
willing to put some time into fixing this, if we can get a timely
update released in the affected package.
Sorry to ask, but I'm having with the first step of the buildout process,
the bootstrap.py script. I get the following error:
> Traceback (most recent call last):
File "bootstrap.py", line 76, in <module>
AttributeError: 'NoneType' object has no attribute 'location'
Unfortunately, I have no idea why this error is occurring. I am running on
OS X Leopard and was just trying to bootstrap an empty buildout.cfg file to
get things started. Tried googling the error, but nothing came up.
how can I use setuptools for downloading (and installing) .msi and .exe
on Windows? I need this for extension modules like pygtk, lxml, psycopg2.
Or at least for finding the files within a html page, like easy_install
The Tryton ERP system requires quite a lot of dependencies. The
installation is an imposition to the user when following the
installation instructions at
So I want to write an installation script which bootstraps setuptools
(this part is already done), installs requires eggs (done) and downloads
.msi or .exe where eggs are not available. The later includes GTK+,
Postgresql and some extension modules like pygtk.
A normal Windows installer packages is not what I need here. The script
is indented for a) developers who want to set up their own development
environment and b) users who need to write extensions for their
Since the filenames may vary by version and python-version, (e.g.
pygtk-2.12.1-1.win32-py2.5.exe) I do not want to hard-code these. Esp.
since this would require changing the script quite often. easy_install
already has a feature for finding the best-matching version
Schönen Gruß - Regards
Dipl.-Informatiker (univ.), CISSP, CSSLP
Spezialist für IT-Sicherheit in komplexen Umgebungen
As some of you may know, using lxml on OSX is a big pain because of an
incompatible system version of libxml2. The solution is to ship binary
eggs, which we already do for Windows.
Now, as a first test, Stefan has uploaded this egg:
Now, I'm on OSX 10.5, and I've requested this exact version.
In a virtualenv, this works. It downloads the given binary egg.
In a buildout, it's preferring to download and build the egg itself, and
it calls it lxml-2.2.1-py2.4-macosx-10.3-i386.egg. That's weird, because
this machine has never had OSX 10.3 on it. :(
My Python 2.4.6 is installed via darwinports.
Now, I can probably work around this, but we're trying to ensure that
people have a sane lxml egg that will install cleanly on a number of
platforms. It's therefore pretty important that the average user doesn't
So, I'd like to try and figure out what's going on. How does buildout
decide which egg to look for? Why is easy_install in a virtualenv
behaving differently to my buildout?
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book
At 02:10 PM 6/20/2009 -0700, rupert.thurner wrote:
>there is http://pypi.python.org/pypi/MoinMoin/1.8.4, and
The distribution filename is 'moin-1.8.4', but the package name
registered on Pypi is "MoinMoin". This won't work.
You may be successful by running:
The problem is that the package is mis-registered on PyPI; its
setup.py declares its name "moin", so that is its distribution
filename. However, on PyPI it is indexed as MoinMoin. You may wish
to inform the maintainers of this, so they can update either the
setup.py to use MoinMoin as the name, or change the Pypi registration
to use "moin". Either should work, assuming that the distribution is
able to work with setuptools. (You'll have to try it and see.)
I am trying to use setuptools and EasyInstall to handle dependency
management for me, using a local subversion server. The svn server uses
svnserve, not http. I have the following in my setup call:
install_requires = ["myModule"],
dependency_links = ["svn://myServer.myCompany.com/myModule"],
But setuptools does not like the svn:// URL. I get the following error:
Searching for myModule
Download error: unknown url type: svn -- Some packages may not be
I have also tried using find_links in the setup.cfg, rather than
dependency_links in the setup.py. I get the same result. Here is my
allow_hosts = *.myCompany.com
find_links = svn://myServer.myCompany.com/myModule
The release notes for EasyInstall 0.3a2 say that download support was
added for svn: URLs, which is what makes me think this is supposed to
Is this a bug, or am I doing something wrong, or am I just
misinterpreting what the tool can do?
This email may contain privileged or confidential information, which should only be used for the purpose for which it was sent by Xyratex. No further rights or licenses are granted to use such information. If you are not the intended recipient of this message, please notify the sender by return and delete it. You may not use, copy, disclose or rely on the information contained in it.
Internet email is susceptible to data corruption, interception and unauthorised amendment for which Xyratex does not accept liability. While we have taken reasonable precautions to ensure that this email is free of viruses, Xyratex does not accept liability for the presence of any computer viruses in this email, nor for any losses caused as a result of viruses.
Xyratex Technology Limited (03134912), Registered in England & Wales, Registered Office, Langstone Road, Havant, Hampshire, PO9 1SA.
The Xyratex group of companies also includes, Xyratex Ltd, registered in Bermuda, Xyratex International Inc, registered in California, Xyratex (Malaysia) Sdn Bhd registered in Malaysia, Xyratex Technology (Wuxi) Co Ltd registered in The People's Republic of China and Xyratex Japan Limited registered in Japan.
I remember when snakebite was announced someone had the idea to have a
kind of build bot go into pypi and get all packages sent to it and
automatically compile them on snakebite for all major platforms and
automatically run tests and submit the compiled packages to pypi. Is
anyone working on this?
The biggest problem I see is security, but if people are really
interested in this we could at least try it no?
Automatic testing in many python versions, conversion using 2to3 and
building packages for windows and macosx seems like a very interesting
santagada at gmail.com