On Thu, Feb 14, 2008 at 05:32:31AM +0100, Encolpe Degoute wrote:
Hello,
I obtain write access last week.
Can someone review my first commit (83809) ?
Looking at http://svn.zope.org/?view=revrev=83809 now...
No, that seems wrong. getLink('text', index=42) is useful functionality
and it works
Hi there,
I'm trying to view the content of an object but it seems that my page
template gets nothing from ZODB. It's rendering the same way as if I was
seeing the page template from the file system (as I have no persistent
content). For example:
h2 tal:content=context/name/titlerecipe name
Ronaldo Z. Afonso a écrit :
Hi there,
I'm trying to view the content of an object but it seems that my page
template gets nothing from ZODB. It's rendering the same way as if I was
seeing the page template from the file system (as I have no persistent
content). For example:
h2
Hi. I have done some fairly sophisticated buildouts over the past year
but here's something I have not done with an extension before now that I
thought ought to be possible:
[buildout]
extends = ${some-part:path}/foo/bar.cfg
[some-part]
path = /some/where/on/my/filesystem
This produces an
On Feb 14, 2008, at 2:58 PM, David Pratt wrote:
Hi. I have done some fairly sophisticated buildouts over the past
year but here's something I have not done with an extension before
now that I thought ought to be possible:
[buildout]
extends = ${some-part:path}/foo/bar.cfg
[some-part]
Hi Jim. Thank you for your reply. I use a number of separate config
files for buildouts, some with longer paths - was hoping to shorten them
up a bit to make them clearer (particularly if they originate from same
root).
One other thing that I have not yet seen is using the part name within
On Feb 14, 2008, at 5:59 PM, David Pratt wrote:
One other thing that I have not yet seen is using the part name
within the part which would be useful. Something like:
[foobar]
baz = bar
log = /some/path/${foobar:?}-${foobar:baz}.log
I don't follow the example. I can thing of perhaps
Hi!
I may have a use case where I need an instance to provide marker
interfaces dynamically. That is, under certain conditions I want the
type to say it provides a particular marker interface, and otherwise it
doesn't. It still needs to support the usual by-class and
directly-provided idioms for
Marius Gedminas a écrit :
On Thu, Feb 14, 2008 at 05:32:31AM +0100, Encolpe Degoute wrote:
Hello,
I obtain write access last week.
Can someone review my first commit (83809) ?
Looking at http://svn.zope.org/?view=revrev=83809 now...
I was not registered in commit mailing list then nobody
Hi Jim. I think ${name} or ${part} would be good.
Sorry for poor example. baz in prev example could be a version or other
differentiating information to form a path name. Here's a better example
though there is many places this could be used.
extra-options =
David Pratt wrote:
Hi Jim. I think ${name} or ${part} would be good.
Sorry for poor example. baz in prev example could be a version or other
differentiating information to form a path name. Here's a better example
though there is many places this could be used.
extra-options =
On Thursday 14 February 2008, Marius Gedminas wrote:
Browser was last modified in rev 71429, IBrowser was last modified in
rev 40065. I guess the person who added the index argument forgot to
update the interface definition.
That was me. :-)
Regards,
Stephan
--
Stephan Richter
Web Software
I'm was curious and try to dig into..
In zope.interfaces.declarations.py __providedBy__ is an instance of
objectSpecificationDescriptor implemented in C
and there is one Python version too in ObjectSpecificationDescriptorPy.
It's a descriptor that try to acess __provides__ of instance and class
13 matches
Mail list logo
