[Zope] Zope 2.5 release?

Pedro B. Gomes Costa pbeck@ciberbit.pt
Thu, 10 Jan 2002 11:51:09 -0000


Hi!

But CoreSessionTracking sessions are different from the ones of 2.5. If i
use them, then i will have to port my code to 2.5 in the future...


----- Original Message -----
From: "Chris McDonough" <chrism@zope.com>
To: "Tim Hicks" <timNOT_THIS@sitefusion.co.uk>
Cc: "Pedro B. Gomes Costa" <pbeck@ciberbit.pt>; "Milos Prudek"
<milos.prudek@tiscali.cz>; <zope@zope.org>
Sent: Wednesday, January 09, 2002 11:24 PM
Subject: Re: [Zope] Zope 2.5 release?


> You should really just install CoreSessionTracking on 2.5 instead and
> transition when you want to.  It's doable; CST will be supported for
> about a year.
>
> Tim Hicks wrote:
>
> >>Hi!
> >>
> >>But, I agree with you abaou the potencial problems of using 2.5.0 on a
> >>production server, but I have this problem:
> >>
> >>I need to use sessions and the way 2.5.0 handle sessions is different
from
> >>the installable products on 2.4.3.
> >>As I'm designing my apps with 2.5.0, I have to use it in production....
> >>Is there a way to use the session functions in 2.5.0 in 2.4.3 ?
> >>
> >
> > I'm having this same dilemma at the moment.  I started off developing on
> > 2.5.0.b2, but got burnt by zserver instabilities and various other
things.
> > As a result, I shifted all the way back down to 2.3.3 (the last of the
> > python 1.5.2 line) which is far more stable on my dev server.  Now
things
> > are working, I'm reluctant to try something potentially less stable.
But...
> > I'm going to be using sessions and I want my code to be portable to any
(at
> > least, most) zope versions, particularly future ones.
> >
> > One solution I thought of was to put all my session stuff (a shopping
> > basket) in one script and test which zope version I'm using at the top.
If
> > the version > 2.43, then use the new syntax, else use the old.  I don't
know
> > if this is a runner as I haven't looked at how the new session stuff has
> > changed yet.  In case anyone's interested, I've made this little script
to
> > find out what version of zope I'm in and return it as a float of the
form
> > x.xx (as opposed to x.x.x as the actual versions are named).  See below.
> >
> > If anyone wants to chip in and tell me it won't work before I try it,
feel
> > free.
> >
> > tim
> >
> > ## Script (Python) "getVersion"
> > ##bind container=container
> > ##bind context=context
> > ##bind namespace=
> > ##bind script=script
> > ##bind subpath=traverse_subpath
> > ##parameters=
> > ##title=Returns the Zope version as a float
> > ##
> > import string
> >
> > vsn = context.Control_Panel.version_txt()[6:11]
> > vsnsplit = string.split(vsn, '.')
> > vsndec = string.join(vsnsplit[1:], '')
> > vsnfloat = '%s.%s' % (vsnsplit[0], vsndec)
> > vsnfloat = string.atof(vsnfloat)
> >
> > return vsnfloat
> >
> >
> >
> >
> >
> >>Thanks
> >>Pedro Costa
> >>
> >>----- Original Message -----
> >>From: "Milos Prudek" <milos.prudek@tiscali.cz>
> >>To: <zope@zope.org>
> >>Sent: Wednesday, January 09, 2002 10:30 AM
> >>Subject: Re: [Zope] Zope 2.5 release?
> >>
> >>
> >>
> >>>Dan Jacobs wrote:
> >>>
> >>>>Hi All,
> >>>>
> >>>>I am currently setting up a new co-location server which will host
> >>>>
> >>several
> >>
> >>>>zope sites (in the UK).
> >>>>
> >>>>Before I install Zope 2.4.3 can anyone tell me how far away we are
> >>>>
> > from
> >
> >>a
> >>
> >>>>stable Zope 2.5?
> >>>>
> >>>I would not install x.x.0 of Zope on a production server if I were you.
> >>>
> >>>In my experience it pays well to wait for x.x.2 or x.x.3. The "zero"
> >>>releases historically contained too much errors for a production
server.
> >>>
> >>>I would, however, heartily recommend to install 2.5.0 as your design
> >>>environment, because the errors are not that annoying and severe, and
> >>>perhaps more importantly, you will be able to influence and help with
> >>>the development of 2.5.1-2.5.3, which will be rock-solid when they come
> >>>out.
> >>>
> >>>Furthermore, sadly, x.x.0 is unlikely to be fully documented, and it
> >>>won't be before x.x.3 that new API is reflected in Zope Book.
> >>>
> >>>This is my take, based on empirical experience :-)
> >>>
> >>>--
> >>>Milos Prudek
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>Zope maillist  -  Zope@zope.org
> >>>http://lists.zope.org/mailman/listinfo/zope
> >>>**   No cross posts or HTML encoding!  **
> >>>(Related lists -
> >>> http://lists.zope.org/mailman/listinfo/zope-announce
> >>> http://lists.zope.org/mailman/listinfo/zope-dev )
> >>>
> >>
> >>_______________________________________________
> >>Zope maillist  -  Zope@zope.org
> >>http://lists.zope.org/mailman/listinfo/zope
> >>**   No cross posts or HTML encoding!  **
> >>(Related lists -
> >> http://lists.zope.org/mailman/listinfo/zope-announce
> >> http://lists.zope.org/mailman/listinfo/zope-dev )
> >>
> >
> >
> > _______________________________________________
> > Zope maillist  -  Zope@zope.org
> > http://lists.zope.org/mailman/listinfo/zope
> > **   No cross posts or HTML encoding!  **
> > (Related lists -
> >  http://lists.zope.org/mailman/listinfo/zope-announce
> >  http://lists.zope.org/mailman/listinfo/zope-dev )
> >
>
>
>
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://lists.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope-dev )