Is there anything I need to do with the mech_browser attribute to send a
custom User-Agent header with zope.testbrowser.browser.Browser?
from zope.testbrowser.browser import Browser
b = Browser()
b.addHeader('User-Agent', 'Zope Test Browser')
b.open('http://localhost/')
Apache
On Fri, 09 May 2008 14:45:38 -0400, Benji York wrote:
There's no way to do a custom User-Agent with just testbrowser. The
way to do it with mechanize is described in
http://wwwsearch.sourceforge.net/mechanize/doc.html, which should work
if used on the mech_browser attribute of a testbrowser
Philipp von Weitershausen wrote:
Is there a pro/con list to including a bootstrap.py in zopeproject for the
other way of using buildout?
I don't quite understand. zopeproject works completely without needing
bootstrap.py. After calling zopeproject, you end up with a completely
I would like to use zopeproject without easy_installing zopeproject and
dependencies into the system python. The steps I'm following lead to a
missing egg-info directory error on the generated project.
This is an svn checkout of zopeproject, but I'd be glad to learn the
recommended way to do
Philipp von Weitershausen wrote:
Yes, I've run into that before as well. As Stefan already pointed out,
virtualenv [1] is great way to create a virtual Python installation
that behaves like a Python installation except that it's just a bunch of
symlinks and *won't* modify the global
This warning has been present when running buildout in fetch-newest mode
for a few weeks. I presume it is due to the svn:// URLs listed on:
http://pypi.python.org/simple/z3c.template/
Getting required 'z3c.template'
required by z3c.formdemo 1.4.0.
Download error: unknown url type:
When running buildout in fetch-newest mode, the following download error
occurs when fetching z3c.template:
Getting required 'z3c.template'
required by z3c.formdemo 1.4.0.
Download error: unknown url type: svn -- Some packages may not be found!
Download error: unknown url type:
Stephan Richter wrote:
Your use case is usually solved using a workflow framework. There are
two workflow frameworks for Zope 3: zope.wfmc/zope.app.wfmc and
hurry.workflow (as Christian pointed out).
WfMC is a very advanced workflow engine based on design by a workflow
coalition.
Luciano Ramalho wrote:
... abundant README.txt files scattered all over the source tree where
the real documentation exists.
Doctest text files are the first and primary resource for me. Packages
published on PyPI with long_description from README.txt+CHANGES.txt are a
much-appreciated
Phillip, thanks for releasing mkzopeapp. I recently got started with a
buildout-enabled zope-3 project by imitating the layout of z3c.formdemo.
How would I use mkzopeapp to create a project.package name like
z3c.formdemo, or is this not generally recommended for application
packages?
Thanks.
--- Stephan Richter [EMAIL PROTECTED] wrote:
I accidently checked in my development buildout.cfg. I fixed that now and
everything should be fine.
Thanks, after the API update there is one class of errors remaining in
AddressBook, with each FormClass occurrence of:
def updateWidgets(self):
Something in z3c.formdemo r77305 gives the following error (r77253 builds
and runs):
$ ./bin/buildout
Develop: '/software/formdemo/.'
Develop: '/software/formdemo/z3c.form'
Traceback (most recent call last):
File /tmp/tmpeS3r2n, line 10, in ?
execfile('/software/formdemo/z3c.form')
12 matches
Mail list logo
