Hi there!
--
DZUG e.V. (Deutschsprachige Zope User Group)
http://www.zope.de
PGP.sig
Description: Signierter Teil der Nachricht
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
Am 25.03.2008 um 10:07 schrieb Jan Ulrich Hasecke:
Hi there!
Ups sorry. This was a more or less automatic mail from linkedin.
There is a zope community group and if you contact the group owner
the mail goes to this list. I think this is not intended. Perhaps
someone can change this in
Hi,
I am experiencing a very strange problem; any thoughts or ideas will
be highly appreciated.
I am using ExtFile 1.5.6 product to store images and files in my
application. During the publishing process, at some point, a rename of
a container with images and files it is involved. From time to
hi every body i'm changing a very old zclass product.
In this zclass i declare a python script with this name mydoc.xls
this script return an xls file with an argument
now i'm writing a zope2 product. How can I explain to zope
that he should publish a certain method with a different name
so when
hi every body i'm changing a very old zclass product.
In this zclass i declare a python script with this name mydoc.xls
this script return an xls file with an argument
now i'm writing a zope2 product. How can I explain to zope
that he should publish a certain method with a different name
so when
Hi there:
I would love to see if there is anyone looking for a student to mentor to do
some hacking in fields such as Python Zope ZODB Grok etc., during this
summer, in the Google Summer of Code 2008.
If you are interested in learning more about my background and experiences
please see my
Maybe a simple solution :
Do you use apache as a frontend for your zope? If you do you can rewrite
the incoming url's for example like this :
RewriteEngine On
RewriteRule ^/folder/mydoc.xls(.*)
http://localhost:8080/VirtualHostBase/http/myIntranet/object_in_zope/VirtualHostRoot/mydoc_xls$1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Jacobs wrote:
Maybe a simple solution :
Do you use apache as a frontend for your zope? If you do you can rewrite
the incoming url's for example like this :
RewriteEngine On
RewriteRule ^/folder/mydoc.xls(.*)
Hi!
Hey, Tres, could you point us to a web example or a web page with more
information about that technique?
I'm very interested on it and the technique that was introduced sometime ago
about how to return a string as __bobo_traverse__ response but the example
was uncompleted (for me at least)
Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
I'm not sure this is all that useful. For Plone 4, we're just going to
have a number of plone.*, plone.app.* and Products.* (and a few others,
like kss.*) eggs that we can put in a KGS or version pin in a single
Plone egg.
For Plone 4
Philipp von Weitershausen wrote:
Andreas Jung wrote:
during the latest 'zope.publisher' thread on zope-dev I came up with
the proposal to eggify the Zope core for the Zope 2.12 release. I
would like to start a discussion about the pros and cons, risks and
advantages of any eggification
Philipp von Weitershausen wrote:
Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
I'm not sure this is all that useful. For Plone 4, we're just going to
have a number of plone.*, plone.app.* and Products.* (and a few others,
like kss.*) eggs that we can put in a KGS or version pin in a
Jim Fulton wrote:
[snip]
Thoughts? Objections?
A simpler publisher has been on my wish-list for a long time now.
I'm a bit worried though that a publisher born from the current Zope 3
publisher with the goal to build up enough support for the Zope 3
publisher to make use of the code will
Hi there,
If you're a student and you want to hack on Zope this summer in the
Google Summer of Code, sign up soon: the deadline is a week from now!
See here for more details:
http://faassen.n--tree.net/blog/view/weblog/2008/03/25/0
Regards,
Martijn
Summary of messages to the zope-tests list.
Period Mon Mar 24 12:00:00 2008 UTC to Tue Mar 25 12:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux
From: Zope Tests
Date: Mon Mar 24 21:58:23 EDT
Matthew Grant wrote:
Just done edits you suggested. Some Unit tests still to be written.
If you wrote the tests first *AS YOU SHOULD* this wouldn't be a problem.
Tests written after the case have a tendency to omit edge cases...
Won't be doing one for that /1000 as tehre are more important
On Mar 25, 2008, at 5:25 AM, Martijn Faassen wrote:
Jim Fulton wrote:
[snip]
Thoughts? Objections?
A simpler publisher has been on my wish-list for a long time now.
I'm a bit worried though that a publisher born from the current Zope
3 publisher with the goal to build up enough support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zope Tests Summarizer wrote:
Summary of messages to the zope-tests list.
Period Mon Mar 24 12:00:00 2008 UTC to Tue Mar 25 12:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Test failures
-
Subject: FAILED
Tres Seaver wrote:
This looks somehow tied to the surgery you were doing yesterday on
zope.testbrowser: can you check it out?
Sure.
time passes
After glancing at it, it looks like Google behaving differently than
expected. Of course, it's a bad idea to make the tests depend on Google
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benji York wrote:
Tres Seaver wrote:
This looks somehow tied to the surgery you were doing yesterday on
zope.testbrowser: can you check it out?
Sure.
time passes
After glancing at it, it looks like Google behaving differently than
Andreas Jung wrote at 2008-3-24 09:00 +0100:
...
Chris favors a 'big' Zope egg with some dependencies (like ZODB) stripped
out. I would prefer a more broader approach. One of the reasons are
company-internals modifications to the Zope core. Right now we maintain a
more or less heavy modified
On Mar 25, 2008, at 4:09 AM, Philipp von Weitershausen wrote:
Philipp von Weitershausen wrote:
Andreas Jung wrote:
during the latest 'zope.publisher' thread on zope-dev I came up with
the proposal to eggify the Zope core for the Zope 2.12 release. I
would like to start a discussion about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Mar 25, 2008, at 5:25 AM, Martijn Faassen wrote:
Jim Fulton wrote:
[snip]
Thoughts? Objections?
A simpler publisher has been on my wish-list for a long time now.
I'm a bit worried though that a publisher born from the
Chris,
FYI - Test coverage in zope.sendmail was originally pretty thin. The
work I have done is a big improvement. Zope.sendmail is a corner of
Zope3 which has not been implemented that well, and this show up in the
terms of its quality and sparse unit test coverage.
Patience please!
Cheers,
I didn't know about zope.publisher.paste, thank you.
I've spent a little bit of time trying to grok zope.publisher.publish
and the IPublication API, and indeed it seems there is almost a one-
for-one mapping between Zope's publication and repoze.obob's helper.
It would almost certainly be
On Mar 25, 2008, at 4:41 PM, Chris McDonough wrote:
...
Two nits:
- I don't like the fact that zope.publisher.publish uses the
setResult API of the request to handle the result returned by the
published object..
You mean the response
why wouldn't it just return the result?
On Mar 25, 2008, at 5:05 PM, Jim Fulton wrote:
On Mar 25, 2008, at 4:41 PM, Chris McDonough wrote:
...
Two nits:
- I don't like the fact that zope.publisher.publish uses the
setResult API of the request to handle the result returned by the
published object..
You mean the response
On Sat, 2008-03-22 at 08:05 +0100, Andreas Jung wrote:
In general we want to get rid of 3rd-party packages we don't want to
maintain on our own.
That's perfectly sane :) There is no sustainable reason to lug around
some other project's code in yours in the Open Source world.
Right now we
Benji York wrote:
Tres Seaver wrote:
This looks somehow tied to the surgery you were doing yesterday on
zope.testbrowser: can you check it out?
I'll take a look at it some more this evening and see if I can figure
out what's up.
The Zope 2 test failures don't look related to my recent
29 matches
Mail list logo
