Hey,
Tim Hoffman wrote:
I thhink just dropping zmi is ploblematical
without a management ui alternative. How would you propose managing
things like per instance pluggable auth components. zcml is not enough
and nor is any other static config. You need per instance persistent
configuration
Hey,
Hermann Himmelbauer wrote:
Am Mittwoch 15 April 2009 09:24:23 schrieb Martijn Faassen:
[snip]
* I'd recommend some people get together and focus on building a much
smaller, more tightly focused replacement of the ZMI that does the
things people find important but is just a single package
Hi there,
Martijn Faassen wrote:
Hermann Himmelbauer wrote:
Am Mittwoch 15 April 2009 09:24:23 schrieb Martijn Faassen:
[snip]
* I'd recommend some people get together and focus on building a much
smaller, more tightly focused replacement of the ZMI that does the
things people find
Hi,
On Wed, 15 Apr 2009 09:37:33 +0200
Martijn Faassen faas...@startifact.com wrote:
Perhaps one way to make the ZMI and optional package is to aggregate the
relevant ZMI code into a smaller amount of packages (or a single
package), for instance zmi.core. The benefit of doing that is that
Summary of messages to the zope-tests list.
Period Tue Apr 14 12:00:00 2009 UTC to Wed Apr 15 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-trunk Python-2.4.6 : Linux
From: Zope Tests
Date: Tue Apr 14 20:50:37 EDT
Yusei TAHARA wrote:
Hi,
On Wed, 15 Apr 2009 09:37:33 +0200
Martijn Faassen faas...@startifact.com wrote:
Perhaps one way to make the ZMI and optional package is to aggregate the
relevant ZMI code into a smaller amount of packages (or a single
package), for instance zmi.core. The
Hi All,
A little gotcha in 2.12 is that, because Versions are now gone, you get
some weird errors when you try and view the ZMI using an older Data.fs.
The following fixed it for me:
cp = app.Control_Panel
cp._objects = tuple([i for i in app._objects if
Hi All,
Chris Withers wrote:
Any ideas what this means or where it's coming from?
Module ZODB.Connection, line 808, in setstate
Module ZODB.Connection, line 876, in _setstate
Module ZODB.serialize, line 604, in setGhostState
Module ZODB.serialize, line 597, in getState
TypeError:
Chris Withers wrote:
Andreas Jung wrote:
Yes, so this change introduced a bug. Who's the right person to fix it?
What's the right collector to report this in?
Since Acquisition is a core module of Zope: the Zope 2 tracker on Launchpad.
Done:
https://bugs.launchpad.net/zope2/+bug/360761
On Wed, 15 Apr 2009 14:10:44 +0200
Martijn Faassen faas...@startifact.com wrote:
Then I'll take this way for now. Maybe z3c.zmi.core would be good?
Flat is better than nested (see the Zen of Python). I'd say go for
zmi.core; z3c isn't necessary.
Thanks. I will use the name zmi.core and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Log message for revision 99146:
Let the permission / directive auto-register permissions that don't exist
already
This kind of test is a poster child for why doctests with lots of
output are fragile: even though it uses
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Log message for revision 99146:
Let the permission / directive auto-register permissions that don't
exist already
This kind of test is a poster child for why doctests with lots of
output are
On Tue, Apr 14, 2009 at 16:46, Jim Fulton j...@zope.com wrote:
Many people have said they're using the Zope 3 app server, where app
server is the collection of components used to run applications using
Zope 3 components.
What no one is interested in is the *application* that was distributed
Yusei TAHARA wrote:
On Wed, 15 Apr 2009 14:10:44 +0200
Martijn Faassen faas...@startifact.com wrote:
Then I'll take this way for now. Maybe z3c.zmi.core would be good?
Flat is better than nested (see the Zen of Python). I'd say go for
zmi.core; z3c isn't necessary.
Thanks. I will use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Hanno Schlichting wrote:
By now I count three people using Zope 3 for a small number of projects.
But none of them seems to have the resources to continue the maintenance
or future development of Zope 3.
Whilst you're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Log message for revision 99146:
Let the permission / directive auto-register permissions that don't
exist already
This kind of test
Andreas Zeidler wrote:
Chris Withers wrote:
https://bugs.launchpad.net/zope2/+bug/360761
Now, who knows how to fix it? ;-)
this has been fixed in http://svn.zope.org/?view=revrev=99191
Wonderful, if Chris can confirm this, I'll make a new Acquisition release.
Hanno
Lennart Regebro wrote:
On Wed, Apr 15, 2009 at 17:09, Martin Aspeli optilude+li...@gmail.com wrote:
I didn't even realise Zope 2.12 was meant to run with Python 2.4. I
thought it was 2.5/2.6 only. Guess I was wrong.
I thought the same, and I'm sure at least Jim said that 2.4 support is
Hanno Schlichting wrote:
Andreas Zeidler wrote:
Chris Withers wrote:
https://bugs.launchpad.net/zope2/+bug/360761
Now, who knows how to fix it? ;-)
this has been fixed in http://svn.zope.org/?view=revrev=99191
Wonderful, if Chris can confirm this, I'll make a new Acquisition release.
Chris Withers wrote:
Hanno Schlichting wrote:
Andreas Zeidler wrote:
Chris Withers wrote:
https://bugs.launchpad.net/zope2/+bug/360761
Now, who knows how to fix it? ;-)
this has been fixed in http://svn.zope.org/?view=revrev=99191
Wonderful, if Chris can confirm this, I'll make a new
Hanno Schlichting wrote:
I've running with a develop copy of the Zope 2 trunk.
Which doesn't include a develop version of Acquisition. Acquisition is
its own package.
Ah, okay, I'll pop Acquisition into develop and test before the end of
this email ;-)
This has include/Acquisition, but is
Chris Withers wrote:
Hanno Schlichting wrote:
This has include/Acquisition, but is that actually being used?
If not, then why is it included like that?
These are only the header files of Acquisition. Some of the C extensions
of the Zope2 egg depend on those headers.
Liar! ;-)
Ok, sigh.
Hanno Schlichting wrote:
If so, then how do I get it to recompile now that I've svn up'ed my Zope
2 trunk to get Andreas' changes?
You need to check out Acquisition from its SVN trunk and include it into
your environment (develop line in buildout or python setup.py
develop). Forcing a
Chris Withers wrote:
Hanno Schlichting wrote:
how would I force recompilation in a buildout environment?
Via python setup.py build_ext -i -f - works in all environments.
Deleting the .so files is probably another way.
I guess that equates to:
bin/buildout setup path/to/setup.py
Hanno Schlichting wrote:
Chris Withers wrote:
Hanno Schlichting wrote:
how would I force recompilation in a buildout environment?
Via python setup.py build_ext -i -f - works in all environments.
Deleting the .so files is probably another way.
I guess that equates to:
bin/buildout setup
Hi.
Uli Fouquet wrote:
As Grok is now approaching the 1.0 release we (i.e. some Grok developers
and me) want to have a 'compliant' way to offer paster-based serving of
Grok instances.
I'd love to have the same for Plone, but failed to find any canonical
definition of compliant the same way
Chris Withers wrote:
A little gotcha in 2.12 is that, because Versions are now gone, you get
some weird errors when you try and view the ZMI using an older Data.fs.
The following fixed it for me:
cp = app.Control_Panel
cp._objects = tuple([i for i in app._objects if
On Apr 15, 2009, at 11:28 AM, Lennart Regebro wrote:
Here are a list of things I have seen that you may mean when you say
Zope 3. I'm sure I missed several:
1. Whatever is included in the Zope 3 tgz that you download.
2. All the packages included in the Zope 3 KGS. (Should be the same as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16.04.2009 1:09 Uhr, Hanno Schlichting wrote:
Chris Withers wrote:
A little gotcha in 2.12 is that, because Versions are now gone, you get
some weird errors when you try and view the ZMI using an older Data.fs.
The following fixed it for me:
29 matches
Mail list logo
