On Tue, 2009-06-30 at 14:35 -0400, Tres Seaver wrote:
> While I know that Mac people often report problems building lxml, I
> never have issues building lxml on Linux: the '--static-deps' option is
> a sufficient workaround for variants with too-old versions of libxml2 /
> libxslt.
I do not know
I'm getting this traceback:
==
serving on http://127.0.0.1:8080
2009-05-17 11:56:42,332 ERROR [SiteError] http://localhost:8080
Traceback (most recent call last):
File
"/home/tim/.buildout/eggs/zope.publisher-3.7.
On Sat, 2009-05-16 at 08:20 +0200, Michael Howitz wrote:
> You use a really ancient version of zope.app.publication. This bug was
> fixed in version 3.5.0 of zope.app.publication. I think at least this
> version is required to be used together with ZODB 3.9.
>
Thanks for pointing this out Mi
I forgot to explicitly ask the question. Where do I file this bug
report?
Thanks,
Tim
On Fri, 2009-05-15 at 10:24 -0300, Tim Cook wrote:
> This is a bug I filed against ZODB3.9.0b1
> As you can see Jim says it is a bug in zope.app.publication but there is
> no Launchpad project to fo
This is a bug I filed against ZODB3.9.0b1
As you can see Jim says it is a bug in zope.app.publication but there is
no Launchpad project to forward the bug to for this module.
The full text of the bug report is below the double lines.
Thanks,
Tim
Forwarded Message
From: Jim Ful
Good analysis Gary,
Though I would tend to see Zope3 as the umbrella and the various
projects (components) under it.
Is there REALLY too much bad press vs. good press about Zope3?
I don't think so. I think inventing a new name ala, Zope Umbrella is a
bad thing. Presenting Zope3 as the Zope
On Wed, 2009-03-25 at 19:21 +0100, Martijn Faassen wrote:
> Why would the steering group be a project as part of the Zope Framework?
> The steering group isn't a project?
>
> I'm all for setting something up, but I'm still not clear on what you'd
> set up. A Zope Framework project group with wh
Hi Dan,
On Sat, 2009-01-17 at 01:28 +0300, Dan Korostelev wrote:
> Hi Tim.
>
> Unfortunately I didn't follow the discussion lately, so may be the
> problem is no more, but...
There has been a tremendous amount of help from folks like you. However
there is still not a solution.
I have been aske
On Thu, 2008-12-18 at 13:00 -0200, Tim Cook wrote:
> This issue is such a huge frustration for me that I am offering a bounty
> of 100USD out of my personal pocket to the first person that solves the
> issue, gets it committed to a published zope.schema egg and included in
> the s
Thanks All,
On Fri, 2009-01-16 at 21:55 +0100, Carsten Senger wrote:
>
> Sure you can have specialized fields that subclass from Field, TextLine,
> or another base class. E.g. RegistrationNumber(TextLine) that takes care
> to validate the input for a special format. But you use them in an
> i
Hi Shane,
On Tue, 2009-01-13 at 14:10 -0700, Shane Hathaway wrote:
> Sorry, but the patch doesn't make any sense. Your version of
> _validate_fields quietly skips validation entirely by default.
First of all that is why I asked for others to look at it. :-)
But I DID test it by inserting an
Thanks for all the assistance.
On Fri, 2009-01-16 at 18:05 +0100, Martijn Faassen wrote:
> Yes, you do create new schema fields by subclassing from Field.
>
> It's just that we saw you putting a field not in a schema but in what
> looked like a concrete object.
This has given me a BIG pause wh
On Fri, 2009-01-16 at 15:55 +0100, Martijn Faassen wrote:
> I don't think a wiki page with a chronicle is necessary or even
> helpful; you need to give us the information necessary to find the
> bug, but no distracting surrounding information.
Okay.
> To debug this
> problem, a developer will n
On Mon, 2009-01-12 at 22:05 +0100, Martijn Faassen wrote:
> Okay, I'll take another look then and look at ObjectRef. Ah, yes, Dan
> pointed out to you that you are using a zope.schema.Field in a class
> instead of in a schema (an interface). That isn't right, and since the
> direct use of that
On Fri, 2009-01-09 at 11:05 +, Chris Withers wrote:
> I can't. The testrunner is already there and buildout-based development
> makes it trivial to run. svn already does the patch creation for you:
>
> $ svn diff
>
> > be able to get past that bit. Perhaps a kind Zope dev will pick up on
>
Thanks Dieter,
On Fri, 2008-12-19 at 19:41 +0100, Dieter Maurer wrote:
> I often approach situations like this with so called "Monkey Patches":
> I replace or enhance classes or methods during startup (triggered
> by some startup event).
>
> This may not be optimal but allows me to solve my probl
Hi Chris,
On Fri, 2008-12-19 at 10:06 +, Chris Withers wrote:
> Tim Cook wrote:
> > As I said before I may have miss-diagnosed the problem and may fix may
> > break other things?
>
> This is what a full-coverage unit and functional test suit is for.
> You have got
Hi Dan,
Thanks for taking a look.
On Thu, 2008-12-18 at 20:06 +0300, Dan Korostelev wrote:
> Hi, Tim.
>
> I builded out your application and took a quick look at the error. It
> looks like you're mis-using the zope.schema.Field class and its
> interface. It should be only used in schema definiti
OOOPS! I forgot to provide the link to the installation instructions:
http://www.openehr.org/wiki/display/dev/OSHIP+Installation
--Tim
On Thu, 2008-12-18 at 13:00 -0200, Tim Cook wrote:
> Based on private responses I have received I would like to clarify some
> things.
>
> I f
08-12-18 at 08:35 -0200, Tim Cook wrote:
> Hi All,
>
> I have had an issue on the table for months. I started a dialog about
> it here:
>
> http://mail.zope.org/pipermail/zope3-users/2008-October/008215.html
>
> The thread was interesting, helpful and did lead me to f
Hi All,
I have had an issue on the table for months. I started a dialog about
it here:
http://mail.zope.org/pipermail/zope3-users/2008-October/008215.html
The thread was interesting, helpful and did lead me to find an error in
some schema definitions because of a misunderstanding of the requi
Hi All,
I started a conversation on the Zope Users list back in October about an
issue I had with the Object field in zope.schema.
http://mail.zope.org/pipermail/zope3-users/2008-October/008215.html
After comments acknowledging that this is a real problem there still
wasn't any activity on it.
Now that ZCA is working with Python 2.5 on 32 and 64 bit platforms
(thanks guys!)
Is there a plan being formulated to address all the deprecation warnings
about 'with' becoming a reserved word in Python2.6?
Thanks,
--Tim
___
Zope-Dev maillist - Z
I have reported Bug 248380: on this issue.
The problem seems to me to be in building the .c modules. That causes
the MemoryError that Lorenzo reported but it isn't the root of the
problem. There are a large number of "warning: initialization from
incompatible pointer type" issues.
--Tim
On
On Thu, 2008-06-26 at 13:14 -0700, Paul Carduner wrote:
> On Thu, Jun 26, 2008 at 1:06 PM, Martijn Faassen <[EMAIL PROTECTED]> wrote:
> > Hi there,
> >
> > I'm curious about the plans of Zope 3 on Python 2.5.
> >
> > * Are people using Zope 3 with Python 2.5 already? What are your
> > experiences?
On Sat, 2008-06-14 at 13:10 +0200, Christian Theune wrote:
> That's exactly the behaviour I was afraid of.
>
> I propose to keep it around for a few more days to see how it stabilizes. If
> it jerks again, I'll switch off notifications until I get a change done that
> avoids this behaviour.
>
>
26 matches
Mail list logo
