Re: [Zope-dev] Zope 2.12 features

On Fri, Oct 31, 2008 at 4:28 AM, Andreas Jung <[EMAIL PROTECTED]> wrote: > If Sidnei should be successful with making Plone 2.11 compatible with Python > 2.5 then we might add "inofficial" support for Python 2.5 to the current > Zope 2.11 release...but as stated earlier I would like to see some arg

Re: [Zope-dev] Zope 2.12 features

On 30.10.2008 21:41 Uhr, Tres Seaver wrote: > From a Zope perspective 2.11 should have had Python 2.5 support, but nobody cared enough to make it happen. We can support Python 2.4 and 2.5 alone in Zope 2.12 and release it in the next months. We should do a 2.12 very soon (before year end, lik

Re: [Zope-dev] Zope 2.12 features

Tres Seaver wrote: > Hanno Schlichting wrote: > I'm fine with having Plone 4 able to run on a 2.6-compatible Zope2. If > we add Python 2.6 to the supported list for a no-later-than Q3 2009 Zope > release, that should be sufficient, no? Sure! >> From a Zope perspective 2.11 should have had Python

Re: [Zope-dev] Zope 2.12 features

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: > Tres Seaver wrote: >> Hanno Schlichting wrote: >>> Here's a list of things I'd like to see in a 2.12 release: >>> - Official Python 2.5 and 2.6 support (almost done, requires a community >>> decision on when we call Restriced

Re: [Zope-dev] Zope 2.12 features

Tres Seaver wrote: > Hanno Schlichting wrote: >> Here's a list of things I'd like to see in a 2.12 release: > >> - Official Python 2.5 and 2.6 support (almost done, requires a community >> decision on when we call RestricedPython supported and reviewed) > > +1 for 2.5; I'm pretty sure 2.6 is not

Re: [Zope-dev] Zope 2.12 features

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sidnei da Silva wrote: >>> - Official Python 2.5 and 2.6 support (almost done, requires a community >>> decision on when we call RestricedPython supported and reviewed) >> +1 for 2.5; I'm pretty sure 2.6 is not there yet, and may be too hard >> to ai

Re: [Zope-dev] Zope 2.12 features

>> - Official Python 2.5 and 2.6 support (almost done, requires a community >> decision on when we call RestricedPython supported and reviewed) > > +1 for 2.5; I'm pretty sure 2.6 is not there yet, and may be too hard > to aim for in one release. What makes you think so? -- Sidnei da Silva Enfo

Re: [Zope-dev] Zope 2.12 features

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: > Philipp von Weitershausen wrote: >> IMHO we shouldn't worry about 2.10 and 2.11 and just care about 2.12 at >> this point. By now it should work with Python 2.5, right? Let's release >> it soonish. Not only will it bring Py

Re: [Zope-dev] Zope 2.12 features / roadmap

On 30.10.2008 19:38 Uhr, Hanno Schlichting wrote: So from a Plone perspective there is no demand for any soon feature freeze or release of Zope 2 itself. Alpha releases might come in handy during spring next year, but even beta versions are not going to be required or particular useful to us.

Re: [Zope-dev] Zope 2.12 features / roadmap

Andreas Jung wrote: > I think there is need for setting a release date right now - I know that > this a total contradiction to our former approach with time-based > releases. The current 2.11 codebase is pretty much in sync with the > latest Zope web-components. Since the Zope 2 development is in p

Re: [Zope-dev] Zope 2.12 features

On 30.10.2008 18:01 Uhr, Lennart Regebro wrote: On Thu, Oct 30, 2008 at 15:03, Hanno Schlichting<[EMAIL PROTECTED]> wrote: - Reconsider getting rid of ZClasses +1 I have some things I want to do when it coms to timezones, so I would like to mentally prepare me for about what release date we

Re: [Zope-dev] Zope 2.12 features

On Thu, Oct 30, 2008 at 15:03, Hanno Schlichting <[EMAIL PROTECTED]> wrote: > - Reconsider getting rid of ZClasses +1 I have some things I want to do when it coms to timezones, so I would like to mentally prepare me for about what release date we are talking about here, so I know when I have to d

[Zope-dev] Bristow T has sent you a private message

Title: Private Message from Bristow Bristow T has sent you a private message Click to read messagePlease read it or Bristow will think you ignored this :( This message has been forwarded at the request of [EMAIL PROTECTED]. To block all emails from FanIQ, please click here. FanI

Re: [Zope-dev] Zope 2.12 features

Previously Hanno Schlichting wrote: > Still I'd put my list out here. Maybe there are others who have been > thinking into the same direction. Here's a list of things I'd like to > see in a 2.12 release: > > - Reconsider getting rid of ZClasses > > I know this one is not popular, but from what I

Re: [Zope-dev] [Checkins] SVN: zc.recipe.cmmi/trunk/README.txt Corrected the link to the SVN repository; I had put in the direct one via

On Oct 30, 2008, at 8:59 AM, Benji York wrote: > On Thu, Oct 30, 2008 at 8:15 AM, Jeff Rush <[EMAIL PROTECTED]> wrote: >> Log message for revision 92695: >> Corrected the link to the SVN repository; I had put in the direct >> one via >> svn+ssh when it should have been the one accessed via http

[Zope-dev] Zope 2.12 features

Philipp von Weitershausen wrote: > IMHO we shouldn't worry about 2.10 and 2.11 and just care about 2.12 at > this point. By now it should work with Python 2.5, right? Let's release > it soonish. Not only will it bring Python 2.5 compatibility but it also > gets rid of Acquisition-wrapped views a

Re: [Zope-dev] acquisition of REQUEST?

Jürgen Herrmann wrote: > i'm searching for the code where acquisition of "aPersistent.REQUEST" is > handled > in zope 2.10? ZPublisher.BaseRequest in the traverse method line 401: # Traverse the URL to find the object: if hasattr(object, '__of__'): # Try to bind the top-level object to the r

Re: [Zope-dev] [Checkins] SVN: zc.recipe.cmmi/trunk/README.txt Corrected the link to the SVN repository; I had put in the direct one via

On Thu, Oct 30, 2008 at 8:15 AM, Jeff Rush <[EMAIL PROTECTED]> wrote: > Log message for revision 92695: > Corrected the link to the SVN repository; I had put in the direct one via > svn+ssh when it should have been the one accessed via http. > - >

[Zope-dev] acquisition of REQUEST?

hi there! i'm searching for the code where acquisition of "aPersistent.REQUEST" is handled in zope 2.10? can someone please point me in the right direction here? i searched the code for 2 hours now and can't find it... thanks in advance and best regards, jürgen herrmann _

[Zope-dev] Zope Tests: 4 OK, 1 Failed, 1 Unknown

Summary of messages to the zope-tests list. Period Wed Oct 29 12:00:00 2008 UTC to Thu Oct 30 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures - Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Thu Oct 30 03:18:23 EDT 200

Re: [Zope-dev] Proposal: Backporting some Python 2.5/2.6 fixes

Andreas Jung wrote: > On 27.10.2008 18:55 Uhr, Sidnei da Silva wrote: >> On Mon, Oct 27, 2008 at 3:42 PM, Andreas Jung<[EMAIL PROTECTED]> wrote: >>> Why do we need these backports on the current maintenance branches? >> >> They are small cleanups that could potentially allow someone to run >> Pyth

Re: [Zope-dev] Proposal: Backporting some Python 2.5/2.6 fixes

Hanno Schlichting wrote: >>> Would anyone be against this? >> I find this pretty disturbing as it implies you *would* be running Zope >> 2.10 on Python 2.5 or 2.6 without fixing RestrictedPython. > > RestrictedPython is its own package. ...which python scripts and page templates rely on heavilly

Re: [Zope-dev] Proposal: Backporting some Python 2.5/2.6 fixes

Chris Withers wrote: > Sidnei da Silva wrote: >> I would like to propose backporting some of the fixes needed for >> Python 2.5 and 2.6 all the way down to Zope 2.10. >> I would *not* backport changes to RestrictedPython because >> those are actually features (support for newer versions of Python)

Re: [Zope-dev] Proposal: Backporting some Python 2.5/2.6 fixes

Sidnei da Silva wrote: > I would like to propose backporting some of the fixes needed for > Python 2.5 and 2.6 all the way down to Zope 2.10. The fixes that would > be backported would only be those that deal with syntax changes (eg: > 'with' and 'as' keyword being used as variables, relative impor