As announced earlier I plan to release Zope 2.8.7 and 2.9.2 by
next Monday...so as always: any pending fixes should be commited
until Monday.
Andreas
pgpnNv3KkZAp4.pgp
Description: PGP signature
___
Zope-Dev maillist - Zope-Dev@zope.org
Zope supports the export of content either through Python pickles (.zexp)
or as XML. Unfortunatly the XML export/import has several problems:
- the generated XML is pretty much too low-level to use it e.g.
for migration issues
- it was broken multiple times in the past, it still has problems
Hello,
Em Sexta, 24 de Março de 2006 15:44, escreveu:
I propose to deprecate XML export/import for Zope 2.10 and to remove it in
Zope 2.12. We don't loose any functionality since .zexp is working fine. I
don't know of any active projects/code that really uses XML export/import.
I've exported
Andreas Jung wrote:
Zope supports the export of content either through Python pickles
(.zexp) or as XML. Unfortunatly the XML export/import has several problems:
- the generated XML is pretty much too low-level to use it e.g.
for migration issues
I have been working on a Zope 2 project
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:07, Jim Fulton wrote:
I think the XML export is a facility that is and should be advertized
as a legitimate escape hatch for data kept in Zope. People really
shouldn't feel afraid of putting data in Zope/ZODB as there
really
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:07, Jim Fulton wrote:
I think the XML export is a facility that is and should be advertized
as a legitimate escape hatch for data kept in Zope. People really
shouldn't feel afraid of putting data in
On the subject of deprecation, for the record, I think removing
ZClasses is a mistake. They have legitimate uses. They have major
flaws too. It would help if we would more clearly document their
limitations and pitfalls, rather than get rid of them, at least
until we have something better,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:12, Jim Fulton wrote:
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:07, Jim Fulton wrote:
I think the XML export is a facility that is and should be
advertized
as a legitimate
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:12, Jim Fulton wrote:
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:07, Jim Fulton wrote:
I think the XML export is a facility that is and should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:25, Jim Fulton wrote:
On the subject of deprecation, for the record, I think removing
ZClasses is a mistake. They have legitimate uses. They have major
flaws too. It would help if we would more clearly document their
On Fri, 24 Mar 2006, Jim Fulton wrote:
Andreas Jung wrote:
I propose to deprecate XML export/import for Zope 2.10 and to remove it
in Zope 2.12. We don't loose any functionality since .zexp is working
fine. I don't know of any active projects/code that really uses XML
export/import.
--On 24. März 2006 11:07:06 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
Andreas Jung wrote:
Zope supports the export of content either through Python pickles
(.zexp) or as XML. Unfortunatly the XML export/import has several
problems:
- the generated XML is pretty much too low-level to use it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:30, Jim Fulton wrote:
Interesting. I imagine that this is fixible in a somewhat
straightforward
way, although it is probably tied up with the general encoding
mess in Z2.
Yes, that's likely where the problem comes from.
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24 Mar 2006, at 16:25, Jim Fulton wrote:
On the subject of deprecation, for the record, I think removing
ZClasses is a mistake. They have legitimate uses. They have major
flaws too. It would help if we would more
--On 24. März 2006 11:25:53 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
On the subject of deprecation, for the record, I think removing
ZClasses is a mistake. They have legitimate uses.
I don't think that ZClasses have real use in the current Zope world except
for legacy code. Most people
Andreas Jung wrote:
...
Right, but for duplicate functionality that is not widely used and that
I consider buggy it is legitimate to propose the deprecation. But as
usually I am open to good arguments :-)
I don't see this as primarily a duplicate feature. I find the export
aspect to be
Andreas Jung wrote:
--On 24. März 2006 11:25:53 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
On the subject of deprecation, for the record, I think removing
ZClasses is a mistake. They have legitimate uses.
I don't think that ZClasses have real use in the current Zope world
except for
On Friday 24 March 2006 17:33, Andreas Jung wrote:
- it has no maintainer, nobody wants to touch it without gloves
Is that any more true than for lots of other things?
Right, but for duplicate functionality that is not widely used and that I
consider buggy it is legitimate to propose the
--On 24. März 2006 11:25:53 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
On the subject of deprecation, for the record, I think removing
ZClasses is a mistake. They have legitimate uses. They have major
flaws too. It would help if we would more clearly document their
limitations and
Andreas Jung wrote:
--On 24. März 2006 11:25:53 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
On the subject of deprecation, for the record, I think removing
ZClasses is a mistake. They have legitimate uses. They have major
flaws too. It would help if we would more clearly document their
--On 24. März 2006 12:03:42 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
There are lots of people who have good uses for ZClasses for
quick one-off projects. I've heard from some of them.
There are lots of people who use Zope who don't fit this
definition. I care about these people. :)
--On 24. März 2006 18:09:36 +0100 Yoshinori Okuji [EMAIL PROTECTED] wrote:
On Friday 24 March 2006 17:33, Andreas Jung wrote:
- it has no maintainer, nobody wants to touch it without gloves
Is that any more true than for lots of other things?
Right, but for duplicate functionality that
Yoshinori Okuji wrote:
On Friday 24 March 2006 17:33, Andreas Jung wrote:
- it has no maintainer, nobody wants to touch it without gloves
Is that any more true than for lots of other things?
Right, but for duplicate functionality that is not widely used and that I
consider buggy it is
On 3/24/06, Jim Fulton [EMAIL PROTECTED] wrote:
We've had sucess writing XSLT templates to transform the pickle data
into formats easily parsable for particular applications.
As part of a recent task (likely the same one Jim's referring to
here!), I transformed the XML export into another XML
I am interested in maintaining them, documenting them, and upgrading them.
I have been through the code a number of times, and if someone would
spend 15 minutes explaining the high level design decisions, I could
probably keep them up to date. Why do they have multiple properties on
a
Andreas Jung wrote:
--On 24. März 2006 12:03:42 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
There are lots of people who have good uses for ZClasses for
quick one-off projects. I've heard from some of them.
There are lots of people who use Zope who don't fit this
definition. I care
--On 24. März 2006 10:00:46 -0800 Christopher Lozinski
[EMAIL PROTECTED] wrote:
I am interested in maintaining them, documenting them, and upgrading them.
Cool. I think a good starting point would be to update
http://www.plope.com/Books/2_7Edition/CustomZopeObjects.stx
I have been
Christopher Lozinski wrote:
I am interested in maintaining them, documenting them, and upgrading them.
Cool. I urge you to do less first. :)
I have been through the code a number of times, and if someone would
spend 15 minutes explaining the high level design decisions, I could
probably
Jim Fulton wrote at 2006-3-24 11:25 -0500:
On the subject of deprecation, for the record, I think removing
ZClasses is a mistake. They have legitimate uses. They have major
flaws too. It would help if we would more clearly document their
limitations and pitfalls, rather than get rid of them,
Andreas Jung wrote at 2006-3-24 16:44 +0100:
Zope supports the export of content either through Python pickles (.zexp)
or as XML. Unfortunatly the XML export/import has several problems:
- the generated XML is pretty much too low-level to use it e.g.
for migration issues
- it was broken
I don't particularly care one way or the other about ZClasses.
However, I would like to see FileSystemSite made part of the
base distribution.
jim penny
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Andreas Jung wrote:
snip
E.g. on the Plone/Archetypes level
we have some mechanisms to export/import data defined through schemas
That's a good point. For Archetypes-based apps, this might be the way
to go. I think that
--On 24. März 2006 16:20:07 -0500 [EMAIL PROTECTED] wrote:
I don't particularly care one way or the other about ZClasses.
However, I would like to see FileSystemSite made part of the
base distribution.
AFAIK FileSystemSite is something CMF-ish..so it does not belong
to the Zope core.
-aj
--On 24. März 2006 21:05:49 +0100 Dieter Maurer [EMAIL PROTECTED]
wrote:
Jim Fulton wrote at 2006-3-24 11:25 -0500:
On the subject of deprecation, for the record, I think removing
ZClasses is a mistake. They have legitimate uses. They have major
flaws too. It would help if we would
--On 24. März 2006 21:05:12 +0100 Dieter Maurer [EMAIL PROTECTED]
wrote:
...
I propose to deprecate XML export/import for Zope 2.10 and to remove it
in Zope 2.12.
What will remain of Zope in the longer run?
The good things that work :-)
In the past with every major release some
35 matches
Mail list logo
