Martijn Faassen wrote:
> Philipp von Weitershausen wrote:
>> Florent Guillaume wrote:
>>> Florent Guillaume wrote:
So here's a proposal: how about having the following order:
- __bobo_traverse__
- unacquired attribute
- zope 3 views
- acquired attributes
>>> Attached is the
Chris Withers wrote:
> Jens Vagelpohl wrote:
>> Use the collector. It is *the* place where people go to look for
>> things to fix. What length of time it takes to fix is a totally
>> separate issue. Bugs that get posted on mailing lists get ignored
>> unless they are "the world is coming to an end"
Chris Withers wrote:
Both core zope and Plone spew forth in their default state.
the deprecation warnings in Plone annoy me to no end. unfortunately, though,
Plone (thus far) has chosen to straddle Zope release. i can't fix the
deprecation warnings that Plone 2.5 generates with Zope 2.9, fo
Chris Withers wrote:
Both core zope and Plone spew forth in their default state.
Zope 2.10 does? It shouldn't. Please point out the deprecation warnings
it sends.
Also could we please bury the zLOG-was-only-halfwy-deprecated issue
that's been beaten to death? Everybody knows there were spur
On 6/20/06, Chris Withers <[EMAIL PROTECTED]> wrote:
I think it's also safe to say that some people will stick with a "good
vintage" zope which has all the features they need and was stable.
And that's OK, and in many cases completely sensible.
--
Lennart Regebro, Nuxeo http://www.nuxeo.com
On 6/20/06, Martijn Faassen <[EMAIL PROTECTED]> wrote:
It broke a lot of stuff for us, so we switched back until we can figure
out what's going on when we upgrade that piece of code to a newer
version of Zope.
There is more tests in Five 1.5, adding them to older version of Five
should be easy.
On 6/20/06, Florent Guillaume <[EMAIL PROTECTED]> wrote:
I was looking at the publisher, and it hacks the URL to explicitely
add the default view to it when a default view is used. That might
explain it. You're saying Zope 2.10 doesn't do that? I thought it did
too.
Well, it adds index_html, no
Florent Guillaume wrote:
On 20 Jun 2006, at 13:23, Martijn Faassen wrote:
[snip]
We've actually noticed Five 1.2.4 is not compatible with Five 1.2 in
some way to do with mysterious 'index.html' bits appearing after URLs
where we thought they shouldn't. We haven't tracked this down and we
migh
On 20 Jun 2006, at 13:23, Martijn Faassen wrote:
Philipp von Weitershausen wrote:
Florent Guillaume wrote:
Florent Guillaume wrote:
So here's a proposal: how about having the following order:
- __bobo_traverse__
- unacquired attribute
- zope 3 views
- acquired attributes
Attached is the curre
Philipp von Weitershausen wrote:
Florent Guillaume wrote:
Florent Guillaume wrote:
So here's a proposal: how about having the following order:
- __bobo_traverse__
- unacquired attribute
- zope 3 views
- acquired attributes
Attached is the current diff I'm working with (for Zope 2.10).
Hey, c
Chris Withers wrote:
> Benji York wrote:
>> Philipp von Weitershausen wrote:
>>> Uh, never mind.
>>
>> +1 :)
>
> Any chance you could explain why you feel that way?
Follow this thread:
http://mail.zope.org/pipermail/zope3-dev/2005-November/016561.html
Philipp
__
Benji York wrote:
Philipp von Weitershausen wrote:
Uh, never mind.
+1 :)
Any chance you could explain why you feel that way?
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Zope-De
Andreas Jung wrote:
I for one, is NOT interested in backporting fixed in Five trunk to
both Five 1.0, 1.1, 1.3, 1.4 and 1.5, which is what are the current
versions of Five if we say that Zope 2.8 and 2.7 should be still
supported after the release of 2.10.
We don't talk about Zope 2.7 which i
As always, Martijn has prettymuch hit the nail on the head with this
mail, +lots to all the points he raises...
Chris
Martijn Faassen wrote:
I think we've concluded a number of things:
* some developers (Andreas in particular) do not consider it a huge
problem to keep maintaining an older v
Martijn Faassen wrote:
Chris Withers wrote:
[snip]
One of my other bugbears is that a flood of deprecation warnings often
masks real problems.
What real problems?
Deprecation warnings in code I need to care about, as opposed to
mindless spew from the zope core or other installed products bu
Lennart Regebro wrote:
Supporting old versions must reasonably be a community effort,
depending on if people have the time to do so. We can't just say
"three versions should be officially supported" and then not doing it.
Yup, and I think it's safe to say the fewer version we need to support,
16 matches
Mail list logo
