There seem to be some problems with packages on sourceforge not working with
buildout. Something about sourceforge is sending two content-length
headers. Anything the buildout gurus here can add?
Description of problem. Suggests just eliminating sourceforge from allowed
hosts:
http://plone.293351
van Rees <
m.van.r...@zestsoftware.nl> wrote:
> Op 12-01-11 23:33, Jeff Kunce schreef:
>
> Hi -
>>
>> I'm having trouble pinning versions in my buildout. It looks like
>> "requires.txt" for the recipe eggs are overriding what I specify in
>> ver
Hi -
I'm having trouble pinning versions in my buildout. It looks like
"requires.txt" for the recipe eggs are overriding what I specify in
versions.cfg.
Here's the scenario:
1) I am pinning my buildout with a versions.cfg file that specifies
zope2 = 2.13.0
2) One of my parts is based o
place for me to start.
-- Jeff
On Wed, Dec 23, 2009 at 1:17 PM, Tarek Ziadé wrote:
> On Wed, Dec 23, 2009 at 10:05 PM, Reinout van Rees
> wrote:
>> On 12/23/09 8:38 PM, Jeff Kunce wrote:
>>>
>>> I am using the buildout page on pypi as a reference
>>>
I am using the buildout page on pypi as a reference
http://pypi.python.org/pypi/zc.buildout
What is the python shell used for the examples? I can follow what is
going on, but I'm not familiar with some of the functions used. For
example:
>>> write(sample_buildout, 'recipes', 'mkdir.py', ...)