Hello,
i want to know how i can convert a ComputedAttribute Object to a String. I have
exactly the problem explain here: http://www.zope.org/Collectors/Ape/19
but i want to have a string in state of a ComputedAttribute Object.
Any Ideas??
Sandra
Sandrine Meyantchop schrieb:
Hello,
i want to know how i can convert a ComputedAttribute Object to a String.
I have exactly the problem explain here:
http://www.zope.org/Collectors/Ape/19
but i want to have a string in state of a ComputedAttribute Object.
Any Ideas??
Sandra
i have only try with str, but the problem is that i want to have for example
the title but str(self.title) return ComputedAttribute object at 0xb7cdb8a0.
--- En date de : Lun 27.4.09, robert rottermann rob...@redcor.ch a écrit :
De: robert rottermann rob...@redcor.ch
Objet: Re: [Zope-dev]
Hi.
Roger Ineichen wrote:
Log message for revision 99518:
Added some BBB code to setDefaultSkin to allow
IBrowserRequest's to continue to work without configuring any
special adapter for IDefaultSkin. Lot's of code inside Zope2
relying on using the request object without tons of CA
Sandrine Meyantchop schrieb:
i have only try with str, but the problem is that i want to have for
example the title but str(self.title) return ComputedAttribute object at
0xb7cdb8a0.
self.title() ??
--- En date de : *Lun 27.4.09, robert rottermann /rob...@redcor.ch/* a
écrit :
De:
What's the reason zope.component.interfaces has no BBB for this
import? The Zope Toolkit is full of 'deprecated()', so why not in this
case?
Stefan
On 27.04.2009, at 03:28, CMF Tests wrote:
CMF Tests : UNKNOWN
CMF-trunk Zope-trunk Python-2.6.1 : Linux
Running
Hi Hanno
Regards
Roger Ineichen
_
END OF MESSAGE
-Ursprüngliche Nachricht-
Von: Hanno Schlichting [mailto:hanno...@hannosch.eu]
Gesendet: Montag, 27. April 2009 09:16
An: d...@projekt01.ch
Betreff: Re: AW: [Checkins] SVN: zope.publisher/trunk/ Added
sorry but self.title() don't work also
--- En date de : Lun 27.4.09, robert rottermann rob...@redcor.ch a écrit :
De: robert rottermann rob...@redcor.ch
Objet: Re: [Zope-dev] ComputedAttribute Object
À: elsand...@yahoo.fr
Cc: Zope-Dev@zope.org
Date: Lundi 27 Avril 2009, 9h23
Sandrine Meyantchop
I do not know
try
Title
Title()
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
Hi there,
Uli Fouquet wrote:
Gary Poster wrote:
I'm concerned about the state of the zc.buildout template recipes. I
want one. I want some one-off files, specific to a certain project,
for which writing a standalone recipe feels very heavy.
Here are the template recipes I
Am Montag 27 April 2009 10:59:21 schrieb Sandrine Meyantchop:
sorry but self.title() don't work also
I personally get along in such situations by displaying something
like self.__dict__ or dir(self) in a log file and handling from object to
object if necessary.
Best Regards,
Hermann
--
Uli Fouquet wrote:
I put the sources in a private repository meanwhile. I'd prefer to put
the sources into Zope repository again, but if this is legally too
difficult, they will stay hosted elsewhere.
Why not merge it back to the original recipe in the collective now? Just
tell me your
Summary of messages to the zope-tests list.
Period Sun Apr 26 12:00:00 2009 UTC to Mon Apr 27 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Sun Apr 26 20:42:32 EDT 2009
URL:
Hi.
Roger Ineichen wrote:
Roger Ineichen wrote:
Then there's some tests and description missing proving that
intent. All I could read in the changelog and the skinnable
tests was pointing in the other direction: Making it possible
to use the Skinnable concept without relying on
Andreas Jung wrote:
I have no problem with the changes. You have my blessing if Hanno is ok
with the changes from the Plone prospective.
I'm OK with the changes from the Plone perspective.
I do however have a concern from the Zope perspective ;)
What I'm worried about is what kind of
Hi there,
Hanno Schlichting wrote:
Uli Fouquet wrote:
I put the sources in a private repository meanwhile. I'd prefer to put
the sources into Zope repository again, but if this is legally too
difficult, they will stay hosted elsewhere.
Why not merge it back to the original recipe in
Hey,
Uli Fouquet wrote:
[snip]
Beside this it would really be nice, if one could share code at least in
the Zope-, Plone and collective repositories with less legal hassle. But
I guess this was already discussed extensively here, so I'd better shut
up ;)
Normally the way code is shared is
Hey,
Laurence Rowe wrote:
I've added the ZODB developers guide to the zope2docs buildout
(converting it to rst) and added another article and some more links to
the zodb articles section, but ideally these should live in their own
directory. What do I need to do to make this happen?
Yay!
Does it work with python2.5 / 2.6 ? If not are there plans to do that ?
Best regards,
Ch. Tronche
On Sat, Apr 25, 2009 at 1:23 PM, Andreas Jung li...@zopyx.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I plan to release new releases for Zope 2.9-2.11 over the next weekend.
So if
Hey Jim, others,
Jim Fulton wrote:
[__file__ in setup.py]
Stop talking about this. :)
This is almost certainly a buildout bug that I'll fix.
Just making sure we have some clear conclusions in this thread...
Do we have a buildout bug id we can track so we make sure we don't
forget about
Hi there,
What do people feel about dropping Python 2.4 support in the Zope
Toolkit? I.e. new releases of packages in the Zope Toolkit (handwave
vaguely as we *still* don't have a canonical list) only have to work in
Python 2.5 (and preferably 2.6), not Python 2.4 anymore.
(this won't affect
Martijn Faassen wrote:
Hi there,
What do people feel about dropping Python 2.4 support in the Zope
Toolkit? I.e. new releases of packages in the Zope Toolkit (handwave
vaguely as we *still* don't have a canonical list) only have to work in
Python 2.5 (and preferably 2.6), not Python 2.4
On 27.04.2009 16:38 Uhr, Christophe Tronche wrote:
Does it work with python2.5 / 2.6 ? If not are there plans to do that ?
Best regards,
Ch. Tronche
On Sat, Apr 25, 2009 at 1:23 PM, Andreas Jung li...@zopyx.com
mailto:li...@zopyx.com wrote:
I plan to release new releases for Zope 2.9-2.11
On 27.04.2009 16:44 Uhr, Martijn Faassen wrote:
Hi there,
What do people feel about dropping Python 2.4 support in the Zope
Toolkit? I.e. new releases of packages in the Zope Toolkit (handwave
vaguely as we *still* don't have a canonical list) only have to work in
Python 2.5 (and
On 27.04.2009 16:48 Uhr, Martin Aspeli wrote:
Martijn Faassen wrote:
Hi there,
What do people feel about dropping Python 2.4 support in the Zope
Toolkit? I.e. new releases of packages in the Zope Toolkit (handwave
vaguely as we *still* don't have a canonical list) only have to work in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christophe Tronche wrote:
Does it work with python2.5 / 2.6 ? If not are there plans to do that ?
- - Zope 2.12 prefers python 2.5 / 2.6, and should still run on 2.4.
- - Older versions will continue to be supported only on 2.4 (we can't
make the
Gary Poster wrote:
I'm concerned about the state of the zc.buildout template recipes. I
want one. I want some one-off files, specific to a certain project,
for which writing a standalone recipe feels very heavy.
Here are the template recipes I found:
collective.recipe.template
Uli Fouquet wrote:
In the beginning my code should go into collective.recipe.template
itself (Wichert agreed), but I wasn't granted committer access to the
collective repository yet. Of course I requested to be approval and
waited for weeks, but nothing happened.
I'm sorry to hear that! In
Andreas Jung wrote:
What would be disappointing?
To be unable to use new packages from an updated Zope Toolkit.
It may be that some (many?) packages won't work with Zope 2.10, but if
we get the kind of dependency isolation we're talking about, I'd wager
that quite a few packages would work
Martijn Faassen wrote:
What do people feel about dropping Python 2.4 support in the Zope
Toolkit? I.e. new releases of packages in the Zope Toolkit (handwave
vaguely as we *still* don't have a canonical list) only have to work in
Python 2.5 (and preferably 2.6), not Python 2.4 anymore.
On 27.04.2009 17:07 Uhr, Martin Aspeli wrote:
Andreas Jung wrote:
What would be disappointing?
To be unable to use new packages from an updated Zope Toolkit.
It may be that some (many?) packages won't work with Zope 2.10, but if
we get the kind of dependency isolation we're
Chris Withers wrote:
I'm also about -sys.maxint on these changes for Zope 2.12 as I'd like to
see 2.12 out the door as soon as possible.
Then we have a conflict of interest. My main goal for Zope 2.12 is to be
based on the Zope Toolkit 1.0 release and loose quite some more stuff.
That in
Martin Aspeli wrote:
Andreas Jung wrote:
What would be disappointing?
To be unable to use new packages from an updated Zope Toolkit.
It may be that some (many?) packages won't work with Zope 2.10, but if
we get the kind of dependency isolation we're talking about, I'd wager
that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
The Plone 3.x series will stay on Python 2.4 for a long time yet, so
this would be very disappointing. I can understand it if the maintenance
burden becomes large, or if there are compelling features of 2.5/2.6
that we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Martin Aspeli wrote:
The Plone 3.x series will stay on Python 2.4 for a long time yet, so
this would be very disappointing. I can understand it if the maintenance
burden becomes large, or if there are compelling features of
Andreas Jung wrote:
On 27.04.2009 17:07 Uhr, Martin Aspeli wrote:
Andreas Jung wrote:
What would be disappointing?
To be unable to use new packages from an updated Zope Toolkit.
It may be that some (many?) packages won't work with Zope 2.10, but if
we get the kind of dependency
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Martin Aspeli wrote:
The Plone 3.x series will stay on Python 2.4 for a long time yet, so
this would be very disappointing. I can understand it if the maintenance
burden becomes large, or if there are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Tres Seaver wrote:
Thinking further on this: there is actually not much shiny about the
ZTK: it is going to be equivalent to a cut-down, dependency-stripped,
bbb-cruft-sanded version of the packages already shipping with
Am Montag 27 April 2009 16:44:17 schrieb Martijn Faassen:
Hi there,
What do people feel about dropping Python 2.4 support in the Zope
Toolkit? I.e. new releases of packages in the Zope Toolkit (handwave
vaguely as we *still* don't have a canonical list) only have to work in
Python 2.5 (and
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Tres Seaver wrote:
Thinking further on this: there is actually not much shiny about the
ZTK: it is going to be equivalent to a cut-down, dependency-stripped,
bbb-cruft-sanded version of the packages
Martin Aspeli wrote:
Hi,
First - a quick question: can we treat __name__ and id/getId()/_setId()
as the same, always? OFS.SimpleItem has some support for letting id and
name be the same, but the link is lost once both __name__ and id are
set. Why isn't __name__ just a property that
Laurence Rowe wrote:
Martin Aspeli wrote:
Hi,
First - a quick question: can we treat __name__ and id/getId()/_setId()
as the same, always? OFS.SimpleItem has some support for letting id and
name be the same, but the link is lost once both __name__ and id are
set. Why isn't __name__ just
Hey,
On Mon, Apr 27, 2009 at 6:39 PM, Hermann Himmelbauer du...@qwer.tk wrote:
It may well be that people (even I myself) use e.g. zope.interfaces or some
other package in some Zope related or unrelated product where it is necessary
due to some other dependencies to maintain Python 2.4
Hi Hanno
Betreff: Re: [Zope-dev] [Checkins] SVN: zope.publisher/trunk/
Added some BBB code to setDefaultSkin
Hi.
Roger Ineichen wrote:
Roger Ineichen wrote:
Then there's some tests and description missing proving
that intent.
All I could read in the changelog and the skinnable
Martin Aspeli wrote:
Laurence Rowe wrote:
Martin Aspeli wrote:
Hi,
First - a quick question: can we treat __name__ and id/getId()/_setId()
as the same, always? OFS.SimpleItem has some support for letting id and
name be the same, but the link is lost once both __name__ and id are
set.
On 4/27/09 3:27 PM, Laurence Rowe wrote:
Martin Aspeli wrote:
Laurence Rowe wrote:
Martin Aspeli wrote:
Hi,
First - a quick question: can we treat __name__ and id/getId()/_setId()
as the same, always? OFS.SimpleItem has some support for letting id and
name be the same, but the link is lost
Now when we have eggs, can we fork the relevant modules (Publisher +
OFS?) into two versions. Zope 2 backwards compatible versions, and
versions that rely on that __parent__ is sane? Plone, and any others
that want to gradually migrate to the toolkit, could then use that
version. People who
Hi Gary,
Previously Gary Poster wrote:
Thanks Uli, Wichert, and Hanno for working out the legal bits! And
thanks to Martijn and Martin for the other replies.
On Friday I had moved to z3c.recipe.filetemplate, for the reasons I
had described then. Philipp said I could run with that
zopyxfil...@gmail.com wrote:
On 27.04.2009 22:56 Uhr, Shane Hathaway wrote:
Lennart Regebro wrote:
Or, we could release 2.12 soon, and then start working on 2.13, a
+1. We need an eggified, Buildout-friendly Zope 2 that's fully
compatible with Zope 2.11.
Zope 2.11???
In
49 matches
Mail list logo
