Notices tagged with zcbuildout
-
#PublicSafetyAnnouncement: do not use #zc.buildout if you value your sanity.
-
about 2 months ago from web -
about 2 months ago from web -
tl.buildout_apache 0.3 veröffentlicht: http://yaturl.net/2fa7 Nach #bitbucket umgezogen. #python #zc.buildout #apache #modpython #mercurial
about 10 months ago from xmpp -
tl.buildout_gtk 0.2.2 nachgelegt: http://pypi.python.org/pypi/tl.buildout_gtk/0.2.2 #python #zcbuildout #gtk #webkit
about a year ago from xmpp -
tl.buildout_gtk 0.2.1 mit einer Handvoll kleiner Korrekturen veröffentlicht: http://yaturl.net/c8a8 #python #zcbuildout #gtk #webkit
about a year ago from xmpp -
VersionConflict: (mechanize 0.1.11, Requirement.parse('mechanize>=0.2.0')) -- where does that requirement come from? #zc.buildout won't say!
about a year ago from gwibber -
@mgedmin: #zc.buildout handles foo+=bar the way it does because it sees a foo+ key internally, of which there can be only one per section.
about a year ago from xmpp -
Discovered that #zc.buildout supports one and only one use of 'foo += bar' for the same 'foo' in a section of the config file. *headdesk*
about a year ago from gwibber -
for extra injury #zc.buildout doesn't exit with a nonzero status code on error
-
"The version, X, is not consistent with the requirement, 'DISTRO>=Y'." No clue where that requirement comes from. #zc.buildout sucks.
-
turns out #zc.buildout's bootstrap.py doesn't work when you don't have python-setuptools installed into your system !python
-
#zc.buildout: $ bin/buildout --version Error: Invalid option --
Thursday, 26-Nov-09 14:24:47 UTC from web
All Identi.ca content and data are available under the