On 10/28/06, Yoshinori Okuji <[EMAIL PROTECTED]> wrote:
for now, so I don't think I can do that. If it is acceptable to simply fix
the current code, we can provide patches.
Of course it's acceptable. Although it would as previously mentioned
be better if you could check them in yourselves inste
On 10/29/06, Yoshinori Okuji <[EMAIL PROTECTED]> wrote:
IIRC, Jim noted that it would be better to
backport zope3's, while our patches are for zope2's.
See http://mail.zope.org/pipermail/zope-dev/2006-May/027503.html for a
short thread on successfully using xmlpickle. With that recipe and
patch
On Friday 27 October 2006 16:46, Lennart Regebro wrote:
> I would propose that somone that uses this heavily (like the Nexedi
> people), joins the Zope Foundation as a commiter, gets commiter rights
> and holds his or her hands over this functionality. :)
We are definitely willing to help the main
On 10/27/06, Lennart Regebro <[EMAIL PROTECTED]> wrote:
It has not worked for a long time, and that's because not many peopleuse it. But those who do usually uses it a lot, so it would be bad ifit goes away.I would propose that somone that uses this heavily (like the Nexedi
people), joins the Zope
It has not worked for a long time, and that's because not many people
use it. But those who do usually uses it a lot, so it would be bad if
it goes away.
I would propose that somone that uses this heavily (like the Nexedi
people), joins the Zope Foundation as a commiter, gets commiter rights
and
Hi!
I would like to resurrect this thread with my own recent experience.
My problem was to spread a set of zodb objects over several zope
installations. Every installation required some slight modifications to
be applied to original objects (such as usernames and passwords).
So I decided to expor
--On 26. März 2006 09:58:07 +0100 Andreas Jung <[EMAIL PROTECTED]> wrote:
Thanks for the patch (commited for Zope 2.8, 2.9. trunk). This solves at
least the import problems on my side. Unfortunately there are no tests
for export/import so fixing issues is like flying blindfolded.
Although th
--On 25. März 2006 21:40:48 +0100 Yoshinori Okuji <[EMAIL PROTECTED]> wrote:
On Saturday 25 March 2006 15:56, Andreas Jung wrote:
Zope 2.7 throws a BadPickleGet, 12 exception, Zope 2.8 throws
BadPickleGet, 13 and Zope 2.9 raises the described UnicodeDecodeError.
I don't expect that the import
On Saturday 25 March 2006 15:56, Andreas Jung wrote:
> Zope 2.7 throws a BadPickleGet, 12 exception, Zope 2.8 throws
> BadPickleGet, 13 and Zope 2.9 raises the described UnicodeDecodeError.
> I don't expect that the import functionality works for even more complex
> objects. So I consider the whole
--On 24. März 2006 11:07:06 -0500 Jim Fulton <[EMAIL PROTECTED]> wrote:
- it was broken multiple times in the past, it still has problems
How so?
The import functionality seem to be broken since at least Zope 2.7.
I created a DTML method exported it and _tried_ to reimport it.
Zope 2.7
--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 pro
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 bro
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 XM
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 bu
--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 t
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 pro
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 mos
-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. I
--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
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
> > expor
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 adver
-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 es
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 Zop
-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 i
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 late
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 exporte
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
27 matches
Mail list logo
