[opensuse-buildservice] zope project
Hi, some time ago zope stopped working with recent python (2.5 currently) and is stuck with python-2.4 . If you want to know more about this problem, please read bug #221256 . To solve this, I've created zope packages that can live with python-2.5 installed. It'd be fine to have a project for them: python-2.4 - modified, so that it does not collide with python (currently 2.5) zope-python-2.4 - zope that explicitely uses python-2.4 zope3-python-2.4 - zope3 that explicitely uses python-2.4 I suggest a name "zope" for the project since this is purely zope issue. I don't know of any other python program which has stopped working on python-2.5. Thanks for your suggestions, Martin -- Best Regards, Martin Kudlvasr Zope Portal Developer --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: mkudlvasr@suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
hi, devel:languages:python:zope would be too long? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 18 April 2007 15:28:00 wrote Marcus Rueckert:
hi,
devel:languages:python:zope
would be too long?
It does not matter in which language something is implemented for the namespace or do you do this because this zope can only get build "devel:languages:python" project ? I would just use "zope", otherwise we would need also to move the kernel to "devel:C:kernel" for example. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG NÃŒrnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-04-18 15:34:35 +0200, Adrian Schröter wrote:
devel:languages:python:zope
It does not matter in which language something is implemented for the namespace or do you do this because this zope can only get build "devel:languages:python" project ?
the rational is that it might pull in other python libraries. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 18 April 2007 15:42:52 wrote Marcus Rueckert:
On 2007-04-18 15:34:35 +0200, Adrian Schröter wrote:
devel:languages:python:zope
It does not matter in which language something is implemented for the namespace or do you do this because this zope can only get build "devel:languages:python" project ?
the rational is that it might pull in other python libraries.
But from the original distro and not from "devel:languages:python", right ? -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG NÃŒrnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-04-18 15:50:27 +0200, Adrian Schröter wrote:
On Wednesday 18 April 2007 15:42:52 wrote Marcus Rueckert:
On 2007-04-18 15:34:35 +0200, Adrian Schröter wrote:
devel:languages:python:zope
It does not matter in which language something is implemented for the namespace or do you do this because this zope can only get build "devel:languages:python" project ?
the rational is that it might pull in other python libraries.
But from the original distro and not from "devel:languages:python", right ?
no, as the original distro might ship 2.5. and it explicitly needs 2.4 darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 18 April 2007 15:53:50 wrote Marcus Rueckert:
On 2007-04-18 15:50:27 +0200, Adrian Schröter wrote:
On Wednesday 18 April 2007 15:42:52 wrote Marcus Rueckert:
On 2007-04-18 15:34:35 +0200, Adrian Schröter wrote:
devel:languages:python:zope
It does not matter in which language something is implemented for the namespace or do you do this because this zope can only get build "devel:languages:python" project ?
the rational is that it might pull in other python libraries.
But from the original distro and not from "devel:languages:python", right ?
no, as the original distro might ship 2.5. and it explicitly needs 2.4
okay, but keep in mind that the place should remain, when zope is fixed for newer python versions ... -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG NÃŒrnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-04-18 15:55:23 +0200, Adrian Schröter wrote:
okay, but keep in mind that the place should remain, when zope is fixed for newer python versions ...
than we would move it into d:l:python direct darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Marcus Rueckert wrote:
On 2007-04-18 15:55:23 +0200, Adrian Schröter wrote:
okay, but keep in mind that the place should remain, when zope is fixed for newer python versions ...
than we would move it into d:l:python direct
What's so ambiguous about the name 'zope' that it has to be prefixed by / replaced by 'devel:languages:python' or something equally hard to memorize? Never heard of a Perl or Lisp implementation of Zope that would force us to differentiate that way. Why not just use 'zope', put zope and the python-2.4 stuff there and remove it (the python-2.4 stuff) again when Zope is ported? Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Apr 18, 2007 at 05:01:16PM +0200, Michal Marek wrote:
Marcus Rueckert wrote:
On 2007-04-18 15:55:23 +0200, Adrian Schröter wrote:
okay, but keep in mind that the place should remain, when zope is fixed for newer python versions ...
than we would move it into d:l:python direct
What's so ambiguous about the name 'zope' that it has to be prefixed by / replaced by 'devel:languages:python' or something equally hard to memorize? Never heard of a Perl or Lisp implementation of Zope that would force us to differentiate that way. Why not just use 'zope', put zope and the python-2.4 stuff there and remove it (the python-2.4 stuff) again when Zope is ported?
Worthwhile debate ;) devel:languages:xy:zope is about as logical as web:applications:zope or applications:web:zope or server:zope. We already have a server namespace. PHP lives there, and not in devel:languages:php. Zope is not more and not less for developers, than PHP, IMO. Wether zope is being built upon something from other projects is more or less speculation I guess. I'm not aware of a newer python in devel:languages:python, anyway. Therefore, I suggest to use "zope" or "server:zope". Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development
Dr. Peter Poeml wrote:
Worthwhile debate ;)
devel:languages:xy:zope is about as logical as web:applications:zope or applications:web:zope or server:zope.
have you ever thought about exploiting Categories feature (like that in MediaWiki). I think it would solve this namespace problem very well (zope would be just "zope", python would be just "python" but they would belong to certain categories).
We already have a server namespace. PHP lives there, and not in devel:languages:php. Zope is not more and not less for developers, than PHP, IMO.
Wether zope is being built upon something from other projects is more or less speculation I guess.
nothing else, just python
I'm not aware of a newer python in devel:languages:python, anyway.
Therefore, I suggest to use "zope" or "server:zope".
server:zope sounds fine
Peter
Martin -- Best Regards / S pozdravem, Martin Kudlvasr Zope Portal Developer --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: mkudlvasr@suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mittwoch, 18. April 2007, Martin Kudlvasr wrote:
Hi,
some time ago zope stopped working with recent python (2.5 currently) and is stuck with python-2.4 . If you want to know more about this problem, please read bug #221256 .
To solve this, I've created zope packages that can live with python-2.5 installed. It'd be fine to have a project for them:
python-2.4 - modified, so that it does not collide with
python (currently 2.5) zope-python-2.4 - zope that explicitely uses python-2.4 zope3-python-2.4 - zope3 that explicitely uses python-2.4
I suggest a name "zope" for the project since this is purely zope issue. I don't know of any other python program which has stopped working on python-2.5.
Thanks for your suggestions,
I've just double-checked: While Zope 2.8.9 (latest from 2007-03-25) does work
with Python 2.4, the supported Python version is 2.3.5. If we have to ship it
with its own Python, shouldn't we use the supported one, not the last one
known to not cause major problems?
OTOH as Zope3 explicitly needs a Python 2.4.4 we'd need to separate the two.
So maybe the Python 2.4.x choice is an acceptable compromise ...
BTW, do we have any feedback from the Zope community if they want to get rid
of this problem any time soon? I'm a big Zope fan in general, but this
requiring a certain Python version really causes more problems that it
should.
Cheers
Joachim
--
Joachim Werner
Joachim Werner wrote:
I've just double-checked: While Zope 2.8.9 (latest from 2007-03-25) does work with Python 2.4, the supported Python version is 2.3.5. If we have to ship it with its own Python, shouldn't we use the supported one, not the last one known to not cause major problems?
Hi Joe, 2.10.3 is the latest from 2007-03-25 and it has TARGET="2.4.4"
OTOH as Zope3 explicitly needs a Python 2.4.4 we'd need to separate the two. So maybe the Python 2.4.x choice is an acceptable compromise ...
so I only have to update zope (I should do that anyway).
BTW, do we have any feedback from the Zope community if they want to get rid of this problem any time soon? I'm a big Zope fan in general, but this requiring a certain Python version really causes more problems that it should.
As I perceive the problem, Jim Fulton doesn't want to split the man force between seamless upgrade from zope2->zope3 and supporting python-2.5. Yes, it causes problems, but I'm really not sure if things would be better the other way. Martin
Cheers
Joachim
-- Best Regards, Martin Kudlvasr Zope Portal Developer --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: mkudlvasr@suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (6)
-
Adrian Schröter -
Dr. Peter Poeml -
Joachim Werner -
Marcus Rueckert -
Martin Kudlvasr -
Michal Marek