Hi there,
In the lxml project (http://codespeak.net/lxml), we've just noticed the
following problem with lxml eggs: you can easy_install an egg that won't
work for your Python.
This is because Python can be compiled with either 2 or 4 bytes unicode
as its internal representation. Any egg that
Hey,
Any feedback on this? Nobody cares that Python eggs compiled with a
linux distribution version of Python don't run on hand-compiled versions
of Python, and vice versa? I added [setuptools] to the topic in case
that's the convention to get people concerned with those to pay
attention. :)
Hi there,
Normally setuptools is installed system-wide. When you install an egg
using easy_install, the egg itself can count on setuptools being
available, and use for instance its resource management API and
namespace package marking facility. It therefore is unnecessary to users
to mark
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
These downsides are, in practice, pretty minor. My main objection is
that I don't like encouraging people to be sloppy about
dependencies. The counter argument, of course, is that the standard
Hi there,
I'm trying to induce zc.buildout's zc.recipe.egg:custom recipe to build
a library (lxml) against C libraries (libxml2, libxslt) installed in a
custom place, i.e. as parts, such as parts/libxml2/include and
parts/libxml2/lib.
I thought I had that working before and even blogged about
Hey,
Jim Fulton wrote:
I think easy_install and setuptools should provide a similar option
and provide a way (presumably through setup.cfg) to make it the
default. For backward compatibility reasons, it may not be possible
to make this the default policy for setuptools, although,
Hi there,
Currently setup.py allows install_requires to specify the dependencies,
possibly including exact version numbers of a package.
It is however beneficial to only specify the *minimum* of expected
requirements in there, to retain maximum flexibility of use. This means
you'd typically
Michael Hoffman wrote:
Martijn Faassen wrote:
Hi there,
Currently setup.py allows install_requires to specify the dependencies,
possibly including exact version numbers of a package.
It is however beneficial to only specify the *minimum* of expected
requirements in there, to retain
Phillip J. Eby wrote:
At 10:38 PM 9/26/2007 +0200, Martijn Faassen wrote:
[snip]
Note that the previous proposal for having a way to specify or'ed
conditions would allow this, but it isn't going to happen until I get
an 0.6 final out so I can focus on refactoring and new features in 0.7.
I
Martijn Faassen wrote:
[snip]
My first response, not based on actually looking at the proposal is that
a simple 'or' condition would not be sufficient, as the package manager
doesnt' know which clause in the condition to look at to find the
preferred version. My second response upon
Hello,
On Nov 19, 2007 7:18 PM, Phillip J. Eby [EMAIL PROTECTED] wrote:
[snip]
One thing that is not very pretty about 'or' syntax for version
preferences is the repetition of the package name:
zope.interface | zope.interface == 1.2.3
While syntactically valid, the above is meaningless,
Hi there,
I'm trying to write a test that tests the integration between the
'versions' line and the 'develop' line in [buildout]. My expectation is
to see the following behavior from buildout:
if I list a version explicitly in 'versions', and list that package
under 'develop', I expect it to
Chris Withers wrote:
Martijn Faassen wrote:
A long-standing issue with using buildout is that even though it
creates a restricted environment, it still uses the site-packages of
the system
I thought the --no-site-packages stuff had already been implemented and
was just waiting for Jim
Hi there,
I've been waiting for years for a release of buildout that contains
proper isolation from Python's site-packages. The non-isolation is a
major flaw in buildout that makes it SO much harder to write proper
installation instructions for software such as Grok.
We need to wrap Grok's
Hey,
On 07/08/2010 05:15 PM, Adam GROSZER wrote:
[snip]
While:
Installing.
Getting section test.
Initializing part test.
Error: Missing option: buildout:find-links
I can reproduce that error. It also worked the second time for me,
though in my case I added an '-n' option to make
On 07/08/2010 04:45 PM, Fred Drake wrote:
On Thu, Jul 8, 2010 at 10:33 AM, Adam GROSZERagros...@gmail.com wrote:
Right now I even cannot get the buildout trunk bin/buildout'ed on
ubuntu. Does it work for you?
It builds for me (Python 2.6 w/ distribute; haven't tried with
setuptools), but the
Hi there,
On 07/08/2010 05:58 PM, Gary Poster wrote:
If several someones volunteered to help test some kind of manual beta
release, that would be great.
I'd be happy to try such a beta release with Grok and report back.
Regards,
Martijn
___
On 07/08/2010 06:08 PM, Gary Poster wrote:
Please try my branch, with dev.py, as mentioned.
Oops, forgot to try it with dev.py.
Regards,
Martijn
___
Distutils-SIG maillist - Distutils-SIG@python.org
Hi there,
Trying the beta-fix branch on python 2.6.5 with distribute (0.6.13) I
get the following error when bootstrapping:
Downloading
http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg
Traceback (most recent call last):
File string, line 1, in module
File
Hey,
On Thu, Jul 8, 2010 at 6:13 PM, Martijn Faassen faas...@startifact.com wrote:
Trying the beta-fix branch on python 2.6.5 with distribute (0.6.13) I
get the following error when bootstrapping:
Oops, I realized I should use dev.py instead. That does work, but the
tests fail with a lot
Hi there,
Some more detailed feedback about failures (with dev.py this time). My
failures at first glance all seem to look like this:
Error in test
/home/faassen/projects/buildout-betafix/src/zc/buildout/buildout.txt
Traceback (most recent call last):
File /usr/lib/python2.6/unittest.py, line
On Thu, Jul 8, 2010 at 7:04 PM, Gary Poster gary.pos...@canonical.com wrote:
On Jul 8, 2010, at 12:58 PM, Martijn Faassen wrote:
Hey,
On Thu, Jul 8, 2010 at 6:13 PM, Martijn Faassen faas...@startifact.com
wrote:
Trying the beta-fix branch on python 2.6.5 with distribute (0.6.13) I
get
Hey again,
Sorry for the confusion earlier on; I am new to testing buildout
itself and I assumed it was easier than it inevitably is.
Now I'm trying to understand how in the world I'm to set an
environment variable with a period in it (PYTHON2.4, and I assume,
PYTHON2.5); it doesn't seem
23 matches
Mail list logo
