Hi,
There's buildout 1.4.4, 1.5.2 and an alpha of 2.0.
The 2.0 seems to aim at python 3 and is, according to the docs, in a
very early alpha stage, so I'll leave that one out.
What I'm using now is 1.4.4 with the special bootstrap.py that ensures
it picks 1.4.4 instead of a newer one. The
On Tue, Aug 16, 2011 at 7:45 AM, Reinout van Rees rein...@vanrees.org wrote:
But... sticking to ye olde 1.4.4 seems wrong to me. So I phoned my brother
Maurits (hi!) who is working with plone: plone is a heavy buildout user, so
what's the status there? He said plone is basically also still on
Hello,
On Tue, Aug 16, 2011 at 13:45, Reinout van Rees rein...@vanrees.org wrote:
b) Is anyone actually using 1.5.2 with system packages? And by that I mean
that you have a dependency on something like numpy and buildout actually
finds that package locally and won't try and grab it off pypi?
On 16-08-11 14:41, Attila Oláh wrote:
Hello,
On Tue, Aug 16, 2011 at 13:45, Reinout van Reesrein...@vanrees.org wrote:
b) Is anyone actually using 1.5.2 with system packages? And by that I mean
that you have a dependency on something like numpy and buildout actually
finds that package locally
On 16/08/2011 04:45, Reinout van Rees wrote:
Hi,
There's buildout 1.4.4, 1.5.2 and an alpha of 2.0.
I've used 1.5.2 happily for ages, but I don't use the stuff Gary
introduced there...
cheers,
Chris
--
Simplistix - Content Management, Batch Processing Python Consulting
-
On 16/08/2011 05:34, Reinout van Rees wrote:
On 13-08-11 11:15, Chris Withers wrote:
Hi All,
In an effort to make it easier to get involved, I've moved
buildout-versions to github:
https://github.com/Simplistix/buildout-versions
buildout-versions 1.6 requires buildout = 1.5
Your recipe was
Hi,
I've CC'ed in the correct mailing list for these discussions, you should
mail there first in future.
Right, replaying our discussion in it's original order:
On 13/08/2011 04:04, B.Nanda Kishore wrote:
when my buildout.cfg is having content like:
*[buildout]*
On 16-08-11 17:04, Attila Oláh wrote:
Getting required 'nose'
required by vemble 0.
We have the best distribution that satisfies 'nose'.
Egg from site-packages: nose 1.1.2
Getting required 'scipy'
required by vemble 0.
We have the best distribution that satisfies 'scipy'.
Egg from
On Tue, Aug 16, 2011 at 13:45, Reinout van Rees rein...@vanrees.org wrote:
recipe = zc.recipe.egg
zc.recipe.egg can handle the new buildout options? When I want system
packages I use z3.recipe.scripts :
http://pypi.python.org/pypi/z3c.recipe.scripts/
--
Sebastien Douche sdou...@gmail.com
On 16-08-11 17:46, Sebastien Douche wrote:
On Tue, Aug 16, 2011 at 13:45, Reinout van Reesrein...@vanrees.org wrote:
recipe = zc.recipe.egg
zc.recipe.egg can handle the new buildout options? When I want system
packages I use z3.recipe.scripts :
Its not just with Django. I have faced the same problem with a different
custom package
also. I have developed two sample packages(having just a setup.py with name
and version mentioned)
and I have tried installing both those packages using buildout. One of those
packages version number is pinned.
On 16/08/2011 18:31, B.Nanda Kishore wrote:
[buildout]
index=http://localhost:8000/
parts = deps
extensions = buildout-versions
[deps]
recipe = zc.recipe.egg
eggs = PkgA
PkgB==0.1.0
When I ran the buildout, this is the output I got.
[versions]
PkgA = 0.1.0
buildout-versions = 1.6
On 16/08/2011 08:56, Reinout van Rees wrote:
Anyone spot anything suspicious?
Maybe pin numpy to the version provided by the system?
Just a guess and nothing I've tried...
cheers,
Chris
--
Simplistix - Content Management, Batch Processing Python Consulting
-
Well that was something new for me. Having two versions of the same package
in
the same buildout file.
Actually I was installing a few distributions in my workplace. So some
distros have
version pinned in their setup.py install_requires section, and when I run
the buildout
expecting the versions
14 matches
Mail list logo
