On Sat, Nov 01, 2003 at 12:18:47PM +0100, Stefan H. Holek wrote:
| I am also very, very worried about breaking b/w compatibility in Zope 2.
|
| I am responsible for about 15 sites, with say 10 distinct products
| each. Are you saying I have to evaluate/upgrade 150 products because I
| want to go
I am also very, very worried about breaking b/w compatibility in Zope 2.
I am responsible for about 15 sites, with say 10 distinct products
each. Are you saying I have to evaluate/upgrade 150 products because I
want to go to Zope 2.8(9)? No customer is going to pay for that effort
(and I will l
Jim Fulton wrote:
3. Use a hybrid schema. I'll call this the "encapsulated base"
scheme.
Is it possible for the hybrid schema to generate a 'deprecation' warning
for each instance of a class that doesn't match the requirements of the
C3 resolution order when Zope is first started, and thus
Jim Fulton wrote at 2003-10-31 12:14 -0500:
> ...
> Thoughts?
>
> I am worried enough about breaking products that I'm inclined to go
> with option 3.
>
> Does anybody think we ought to use the new algorithm (option 2)?
Please do not use the new algorithm (option 2).
I like (multiple) in
On Fri, Oct 31, 2003 at 02:46:51PM -0500, Jim Fulton wrote:
| >Most of the time, this is the same people who can't update their
| >products, so if they *do* want a new zope, they will need to get a new
| >product as well. I think its safe to make that assumption.
|
| I don't follow this. What do
Sidnei da Silva wrote:
On Fri, Oct 31, 2003 at 12:14:27PM -0500, Jim Fulton wrote:
| Thoughts?
|
| I am worried enough about breaking products that I'm inclined to go
| with option 3.
|
| Does anybody think we ought to use the new algorithm (option 2)?
I'm for option 2. Given that a huge amount
Sidnei da Silva wrote:
| Ohkay. If anyone has a problem, I'll send them to you and Sidnei. :)
/me takes his iBook and a plane to The Amazon
| Note that, in many cases, the people having problems will *not* be the
| product authors. They'll be people who just want to upgrade thier Zope
| inst
On Fri, 2003-10-31 at 13:52, Sidnei da Silva wrote:
> | I personally don't like the new algorithm, but I don't really care
> | in the long run. One should avoid inheritence complex enough to show
> | a difference.
>
> I hearthly agree here.
Home domestic of you .
I do like the new algorithm, but
| Ohkay. If anyone has a problem, I'll send them to you and Sidnei. :)
/me takes his iBook and a plane to The Amazon
| Note that, in many cases, the people having problems will *not* be the
| product authors. They'll be people who just want to upgrade thier Zope
| installationa that use thir
Jeremy Hylton wrote:
I am worried enough about breaking products that I'm inclined to go
with option 3.
Does anybody think we ought to use the new algorithm (option 2)?
I think we should use the new algorithm. However, I don't have any
products that I would be responsible for updating and mainta
> I am worried enough about breaking products that I'm inclined to go
> with option 3.
>
> Does anybody think we ought to use the new algorithm (option 2)?
I think we should use the new algorithm. However, I don't have any
products that I would be responsible for updating and maintaining. I'd
b
On Fri, Oct 31, 2003 at 12:14:27PM -0500, Jim Fulton wrote:
| Thoughts?
|
| I am worried enough about breaking products that I'm inclined to go
| with option 3.
|
| Does anybody think we ought to use the new algorithm (option 2)?
I'm for option 2. Given that a huge amount of software that is bas
I've been working on a "new-style" ExtensionClass (nsEC) project to
reimplement ExtensionClass as a new-style meta class. This will allow
ExtensionClasses (i.e. most Zope 2 classes) to be able to use features
of new-style Python classes, including:
- New protocols,
- Descriptors,
- Garbage Colle
13 matches
Mail list logo
