Re: [Zope-dev] Re: ZPT backward compatibility
On 1/17/06, Tino Wildenhain <[EMAIL PROTECTED]> wrote: > Add to it the fact the zpt@zope.org was due to be retired > anyway ;) Though retirement for the list was discussed, it was decided not to retire it since it was still the best place for implementors to discuss matters. The implementations in Zope 2 and Zope 3 are not the only implementations, and the other implementors are justifiably not interested in joining Zope-specific lists. -Fred -- Fred L. Drake, Jr. "There is no wealth but life." --John Ruskin ___ 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 http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: ZPT backward compatibility
Dieter Maurer schrieb: > Andreas Jung wrote at 2006-1-16 19:55 +0100: ... > I have seen some answers -- though not too many... > > Note also that "zpt@zope.org" is a very low activity list. > For it, a few answers is already a lot... Add to it the fact the zpt@zope.org was due to be retired anyway ;) ___ 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 http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: ZPT backward compatibility
Andreas Jung wrote at 2006-1-16 19:55 +0100: > ... >Well, I brought this issue up on zope-dev to discuss this issue directly. >but with almost zero feedback :-) Also another related posting to zope-zpt >got _zero_ anwers. I have seen some answers -- though not too many... Note also that "zpt@zope.org" is a very low activity list. For it, a few answers is already a lot... -- Dieter ___ 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 http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZPT backward compatibility
Jim Fulton wrote at 2006-1-16 13:36 -0500: > ... >2. If we decide to change something, even if it's backward incompatible, >we need to change Zope itself to do things the new way before we expect >other people to and before we introduce the deprecation warning. >If there isn't a valid new way of doing something, then we can't deprecate >the old way. I am very happy that you write this. -- Dieter ___ 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 http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Deprecation process issues
Tres Seaver wrote: I've noticed a couple of problems with recent deprecation decisions (for OFS.content_types and zLOG). The major one is that the deprecation warning waw added without removing the code in the core which depends on the deprecated feature. The most obvious sign of this is that the tests no longer "run clean", but are cluttered up with warning output. Yes this is a major pain. Such that in my sandboxes the first thing I do is comment out the warning in zLOG. Florent Another issue is that at least one of those choices (the zLOG one) seemed to land without accounting for the legitimate use cases which the new "blessed" method doesn't address (e.g, logging levels not offered by the standard 'logging' module). I'm about to check in changes which clean out the use of OFS.content_types, but am less willing to clean up the zLOG uses until the other use cases are addressed. -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ 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 http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope tests: 8 OK
Summary of messages to the zope-tests list. Period Mon Jan 16 12:01:02 2006 UTC to Tue Jan 17 12:01:02 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Mon Jan 16 21:02:28 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004026.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Jan 16 21:03:58 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004027.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Jan 16 21:05:28 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004028.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 16 21:06:58 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004029.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Jan 16 21:08:28 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004030.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 16 21:09:58 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004031.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 16 21:11:29 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004032.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Jan 16 21:12:59 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004033.html ___ 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 http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.10] ZPT going Unicode
Dieter Maurer wrote: Tino Wildenhain wrote at 2006-1-13 16:45 +0100: ... Maybe just have new uZPT with Unicode and leave the "old" ZPT allone? Maybe with limited ability to "add" old ZPT from ZMI or such. This would solve the backward-compatibility problems and would be a more smooth transition w/o the need of upgrade hacks and "strict" hacks (after all, we arent perl/php ;)) I fear it is not that easy: Unless we set Python's "defaultencoding" to the site encoding (and we have such a thing), Python cannot mix Unicode and non-Unicode. Thus, your "old" ZPT's would need to use only other old ZPT's and "old" Python scripts and "old" methods (returning encoded texts) while "strict" ZPT's would need to use only new (strict) ZPT's, scripts and methods. Quite unfeasible... Right, and setting Python's default encoding is out of the question. Regards, Martijn ___ 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 http://mail.zope.org/mailman/listinfo/zope )
