Previously Paul Carduner wrote:
Hello zope3-dev,
I came across an error I have not seen before. Just for reference,
here is the last snippet from the traceback:
File
Hi,
after thinking the problem over at gocept we came to the following
suggestion:
- A site is a place which gives acces to a component registry.
- ISite isn't a good name for the concept behind it, because it is
connected too tight to a website and on having hierarchical
structures (at
On 2007-08-09 20:51:26 +0200, Philipp von Weitershausen
[EMAIL PROTECTED] said:
Roman Joost wrote:
we're doing some dependency checking at gocept and I discovered that
zope.annotation depends on zope.app.container in its factory.
What shall we do with this dependency to zope.app.container?
Hi,
zope.traversing has a dependency to zope.app.applicationcontroller. This
is because zope.traversing implements the etc namespace and has a hard
coded reference to applicationcontrol there.
In the same place it also looks up site managers (in a hard coded way).
As a strategy to remove this
Hi,
I saw the error reports about zope.security and got talked to from a few
people that they had severe problems managing around this. I removed the
3.4b4 distribution from download.zope.org to allow them to continue
using zopeproject and grokproject until we find a fix.
I wasn't sure about
On Wednesday 15 August 2007 08:01, Christian Theune wrote:
zope.traversing has a dependency to zope.app.applicationcontroller. This
is because zope.traversing implements the etc namespace and has a hard
coded reference to applicationcontrol there.
In the same place it also looks up site
Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune:
Hi,
I saw the error reports about zope.security and got talked to from a few
people that they had severe problems managing around this. I removed the
3.4b4 distribution from download.zope.org to allow them to continue
using
Previously Christian Theune wrote:
Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune:
Hi,
I saw the error reports about zope.security and got talked to from a few
people that they had severe problems managing around this. I removed the
3.4b4 distribution from
Hey,
Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune:
Hi,
I saw the error reports about zope.security and got talked to from a few
people that they had severe problems managing around this. I removed the
3.4b4 distribution from download.zope.org to allow them to continue
On Wednesday 15 August 2007 07:41, Michael Howitz wrote:
- ISite isn't a good name for the concept behind it, because it is
connected too tight to a website and on having hierarchical
structures (at least in the code).
I think this is a matter of documentation and explanation. Anyone
On Wednesday 15 August 2007 07:43, Christian Zagrodnick wrote:
For the annotation factory using zope.location and ILocatable would be
sufficient. So we could get rid of the zope.app.container dependency.
+1
We should be a bit more specific about the IContained interface. Does
it make any
On Aug 14, 2007, at 7:32 PM, Paul Carduner wrote:
Hello zope3-dev,
I came across an error I have not seen before. Just for reference,
here is the last snippet from the traceback:
File /home/pcardune/Work/ZContact/zcontact-lp/eggs/tmpgwuq6O/
Previously Jim Fulton wrote:
On Aug 14, 2007, at 7:32 PM, Paul Carduner wrote:
Hello zope3-dev,
I came across an error I have not seen before. Just for reference,
here is the last snippet from the traceback:
File /home/pcardune/Work/ZContact/zcontact-lp/eggs/tmpgwuq6O/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Howitz wrote:
Hi,
after thinking the problem over at gocept we came to the following
suggestion:
- A site is a place which gives acces to a component registry.
- ISite isn't a good name for the concept behind it, because it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Aug 14, 2007, at 7:32 PM, Paul Carduner wrote:
Hello zope3-dev,
I came across an error I have not seen before. Just for reference,
here is the last snippet from the traceback:
File
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephan Richter wrote:
On Wednesday 15 August 2007 08:01, Christian Theune wrote:
zope.traversing has a dependency to zope.app.applicationcontroller. This
is because zope.traversing implements the etc namespace and has a hard
coded reference to
On Aug 15, 2007, at 10:34 AM, Tres Seaver wrote:
...
We badly need to get a handle on how we expect people to fetch eggs
for
packages: having such a refactoring affect an indirect client (one
not
expecting to track day-to-day development) is a disaster.
I'm not sure disaster is the word
I've just released a b5 egg which should correct the problem.
Jim
On Aug 15, 2007, at 9:51 AM, Wichert Akkerman wrote:
Previously Jim Fulton wrote:
On Aug 14, 2007, at 7:32 PM, Paul Carduner wrote:
Hello zope3-dev,
I came across an error I have not seen before. Just for reference,
here
Wichert Akkerman wrote:
Previously Christian Theune wrote:
Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune:
Hi,
I saw the error reports about zope.security and got talked to from a few
people that they had severe problems managing around this. I removed the
3.4b4
Christian Theune wrote:
Hey,
Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune:
Hi,
I saw the error reports about zope.security and got talked to from a few
people that they had severe problems managing around this. I removed the
3.4b4 distribution from download.zope.org to
Am Mittwoch, den 15.08.2007, 17:52 +0200 schrieb Martijn Faassen:
Wichert Akkerman wrote:
Previously Christian Theune wrote:
Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune:
Hi,
I saw the error reports about zope.security and got talked to from a few
people that they
On Aug 15, 2007, at 11:52 AM, Martijn Faassen wrote:
Wichert Akkerman wrote:
Previously Christian Theune wrote:
Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune:
Hi,
I saw the error reports about zope.security and got talked to
from a few
people that they had severe
On Aug 15, 2007, at 11:56 AM, Christian Theune wrote:
I'm not sure that we should have to rely on removing packages like
those.
I'm fairly sure that removing them is *not* the right solution. For
example, that might have broken other applications. (After all, I
released b4 for a
Am Mittwoch, den 15.08.2007, 17:59 +0200 schrieb Martijn Faassen:
Where is this b5? I am still getting b4, not b5. I can't find b5 on the
server.
I've put it there now. The actual distribution was missing. I've created
the b5 tag and uploaded the sdist package.
Jim Fulton wrote:
[snip]
Just ran into this one. I think removing it is the right decision. b2
did work for me, but b4 just broke on me.
Try b5.
I'd love to try the mysterious b5, but it's just not there. :)
Regards,
Martijn
___
Zope3-dev
On Aug 15, 2007, at 12:00 PM, Martijn Faassen wrote:
Jim Fulton wrote:
[snip]
Just ran into this one. I think removing it is the right
decision. b2 did work for me, but b4 just broke on me.
Try b5.
I'd love to try the mysterious b5, but it's just not there. :)
I tried to put it there,
Am Mittwoch, den 15.08.2007, 12:02 -0400 schrieb Jim Fulton:
On Aug 15, 2007, at 11:56 AM, Christian Theune wrote:
I'm not sure that we should have to rely on removing packages like
those.
I'm fairly sure that removing them is *not* the right solution. For
example, that might have
Christian Theune wrote:
Am Mittwoch, den 15.08.2007, 17:52 +0200 schrieb Martijn Faassen:
Wichert Akkerman wrote:
Previously Christian Theune wrote:
Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune:
Hi,
I saw the error reports about zope.security and got talked to from a
Thanks for the quick response everybody. Next time I'll be sure to
include the full traceback.
- Paul
On 8/15/07, Jim Fulton [EMAIL PROTECTED] wrote:
I've just released a b5 egg which should correct the problem.
Jim
On Aug 15, 2007, at 9:51 AM, Wichert Akkerman wrote:
Previously Jim
29 matches
Mail list logo
