he original issue. I don't see the reason
why Blob.open shouldn't just ignore the 'b' flag and just give an error
if someone tries to give it a 't'. If that makes it useful in more
cases, I'd be all for it.
Regards
Jacob Holm
_
Hi Adam
Adam GROSZER wrote:
> Hello,
>
> I've run into a misterious issue while evolving generations from an
> old DB.
>
> Quick fact is that it seems like a BTree kept an object reference to
> an object which was deleted from it.
[snip]
Yes, the BTree implementations we use may keep a reference
Hi Malthe
Malthe Borch wrote:
> I've branched out this package and removed the C-extension. It's not
> documented in the package why a C-extension is needed or alternatively,
> what it benefits.
>
> If there are no objections, I will merge this into trunk shortly.
>
>
IIRC, the C extension i
Hi Dan
Dan Korostelev wrote:
> Hi there!
>
> While looking at the zope.app.principalannotation package, I
> discovered that both zope.annotation and zope.app.principalannotation
> register their IAnnotations adapters twice: fisrt, as a simple adapter
> and second, as a multi adapter for some addit
Chris Withers wrote:
> [snip]
> It's interesting, this use case sound pretty close to what I'm talking
> about in the very last part of this message:
>
> http://mail.zope.org/pipermail/zope-dev/2009-March/035220.html
>
> ie: adapter context based on object traversal rather than notion of
> "curre
Wichert Akkerman wrote:
> Previously Martijn Faassen wrote:
>
>> Hey,
>>
>> Stephan Richter wrote:
>> [snip]
>>
>>> There is a compromise I am willing to take. If package zope.bar depends on
>>> a
>>> *new feature* or *feature change* in zope.foo 1.3.x, then it should specify
>>> the ver
Chris Withers wrote:
> Jacob Holm wrote:
>>> Can someone confirm to me whether or not manually specifying the
>>> context as I have in the example above would work, or would I need
>>> to do:
>>>
>>> >>> adapter1 = getAdapter(a,I
Hi Baiju
If this whitespace fix is based on the current style guide, I think the
guide needs to be fixed. I find the fixed version much less readable. A
function that takes this many arguments should have an exception to the
PEP 8 rule of no whitespace around the equals sign used for keyword
a
Michael Howitz wrote:
> Am 01.04.2009 um 23:44 schrieb Jacob Holm:
>
>> Hi Baiju
>>
>> If this whitespace fix is based on the current style guide, I think the
>> guide needs to be fixed. I find the fixed version much less readable. A
>> function that take
Jim Fulton wrote:
> On Apr 2, 2009, at 2:31 PM, Chris Withers wrote:
>
>> For me, the ideal would be simply https for everything and using http
>> basic auth for access with more people having access to update the
>> passwd file and maybe Trac or WebSVN for a nice web interface.
>>
>
>
> I
Michael Howitz wrote:
> Am 12.04.2009 um 15:12 schrieb Michael Howitz:
>> Hi,
>>
>> I'm using a trunk version of z3c.form and have the following
>> situation:
>> In my interface I have a zope.schema.Bytes field.
>> z3c.form.converter.FileUploadDataConverter.toFieldValue returns
>> z3c.form.interf
Martijn Faassen wrote:
> I was thinking people would get behind the following proposal:
>
> IFoo()
>
> for adaptation and multi adaptation (with tuple arguments)
>
> and
>
> IFoo.utility()
>
> for utility lookups.
>
> One argument in favor of using plain calls for multi adaptation (using
> t
Marius Gedminas wrote:
>
> Are you sure that most views provide IBrowserView these days? URL
> traversal looks them up as multi-adapters providing just Interface.
>
True and you will almost never see a view class using
"implements(IBrowserView)" directly. Still, if you use the browser:view
or
Hi,
Roger Ineichen wrote:
Note, if you run the i18nextract script, all module must be there like in a running application. You can't only use the files which will
contain locales. Also modules which this packages import from must be there.
That should not be necessary I think. At least
Hello
This checkin contains the following change to
zope.component/trunk/src/zope/component/registry.py
which looks wrong to me (it's a noop). It looks to me as if the [:2]
should move outside the ")" following it. I am surprised that this
doesn't break any tests, as it means that reregistr
This looks like a bad idea. You are weakening the test by removing
non-ascii chars here. A better approach would have been to rewrite the
non-ascii chars using \N (or \u or \U) escapes.
Regards
- Jacob
Michael Howitz wrote:
> Log message for revision 90434:
> as it seems impossible to u
Hi Michael, Tres
I agree a new major version is required due to the new "feature" of
having new permission names, but there is no reason to break
compatibility with code using the old names.
IIRC the zcml-directive is there exactly to
provide backwards compatibility when renaming permissions.
Hi Tres
Tres Seaver wrote:
> Assuming we put the 'redefinePermssion' directives in place on the
> trunk, why shouldn't we leave the version number as is? I consider the
> rename a bugfix, not a feature, and if we make it backwared compatible,
> there is no reason to bump the major version.
It's
On 2011-07-22 13:26, Brian Sutherland wrote:
> This would be my first guess:
>
> class INode(Interface):
> pass
>
> INode.parent = Object(
> title=u"Parent node",
> schema=INode
> )
>
> INode.children = List(
> title=u'Chil
On 2011-07-22 14:32, Joshua Immanuel wrote:
> Hello,
>
> On Fri, 2011-07-22 at 13:41 +0200, Jacob Holm wrote:
>> On 2011-07-22 13:26, Brian Sutherland wrote:
>>> This would be my first guess:
>>>
>>> class INode(Interface):
>>>
20 matches
Mail list logo
