Fabio Tranchitella wrote:
> Hello,
>
> * 2009-11-16 10:25, Martijn Faassen wrote:
>>> Anyone willing to make a new release of zope.component and zope.sendmmail,
>>> or give me the pypi access to do it?
>> What's your pypi username?
>
> kobold

I've added you for zope.component. You already had release access for
zope.sendmail.

Good luck! As a probably superfluous reminder, make sure to make these
feature (not bugfix) releases. :)

Regards,

Martijn


_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Summary of messages to the zope-tests list.
Period Sun Nov 15 12:00:00 2009 UTC to Mon Nov 16 12:00:00 2009 UTC.
There were 6 messages: 6 from Zope Tests.


Tests passed OK
---------------

Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Sun Nov 15 21:03:31 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013023.html

Subject: OK : Zope-2.11 Python-2.4.6 : Linux
From: Zope Tests
Date: Sun Nov 15 21:05:31 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013024.html

Subject: OK : Zope-2.12 Python-2.6.4 : Linux
From: Zope Tests
Date: Sun Nov 15 21:07:31 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013025.html

Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux
From: Zope Tests
Date: Sun Nov 15 21:09:36 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013026.html

Subject: OK : Zope-trunk Python-2.6.4 : Linux
From: Zope Tests
Date: Sun Nov 15 21:11:36 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013027.html

Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux
From: Zope Tests
Date: Sun Nov 15 21:13:42 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013028.html

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Hello,

* 2009-11-16 10:25, Martijn Faassen wrote:
> > Anyone willing to make a new release of zope.component and zope.sendmmail,
> > or give me the pypi access to do it?
> What's your pypi username?

kobold

Thanks,
Fabio
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Hey,

Fabio Tranchitella wrote:
> Anyone willing to make a new release of zope.component and zope.sendmmail,
> or give me the pypi access to do it?

What's your pypi username?

Regards,

Martijn



_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Yes,

I followed the instructions from the howto, including the mount point part.
I have a folder named 'session_folder' in my root, and it containts a
session data manager. There are also items in there when sessions are
being used so it looks like that's functioning fine.

Are the sessions ID's not consistent accross clients or is this some
kind of bug?

Allen Schmidt Sr. wrote:
> Do you have the ZODB mount point set up and pointing to your
> session_folder?
>
> Marko Kruijer wrote:
>> That's not my problem, the session is in it's own .fs file, and it is
>> persistent.
>> The problem is that the two zope clients use different sessions id's
>> for the same user, that's not supposed to happen imo.
>>
>> Allen Schmidt Sr. wrote:
>>> What we did was create a Session.fs and added to the zope and zeo
>>> conf files. Then after restarting the zopes and zeo, in the ZMI,
>>> create a ZODB mount point and it should see the Session.fs and build
>>> the parts in the root of the ZMI that you need. Been a long time but
>>> I think those are the steps. That way the session data is its own
>>> data.fs file and is persistent across zopes and restarts, etc. The
>>> problem is that it IS a data.fs file and therefore an undoing
>>> storage. You will have to pack it the same as your main data file.
>>> Not a big deal for us as its not used much. Just pack back a couple
>>> days so you don't whip any session data that could be going on at
>>> that moment.
>>>
>>> Anyone please chime in if I am missing something. Just taking a shot
>>> at an answer based on our set up.
>>> Your mileage may vary.
>>>
>>> Allen
>>>
>>>
>>> Marko Kruijer wrote:
>>>> I'm maintaining a ZEO cluster setup that currently consists of 2
>>>> Zope clients and 1 ZEO server (Zope version is 2.10.5.)
>>>>
>>>> I'm using sessions on the hosted site and am having trouble sharing
>>>> them across the 2 servers.
>>>>
>>>> I've done a config as described here:
>>>> http://www.zopelabs.com/cookbook/1061234337
>>>>
>>>> Everything runs fine, except my sessions 'change' randomly. For
>>>> example if I output my SESSION data I notice that the sessions ID
>>>> is not persistent over i.e. 10 page loads.
>>>> The contents of the sessions also change, of course.
>>>>
>>>> Am I missing something here? The central storage of the sessions
>>>> should fix this if i'm correct, but it doesn't.
>>>> Is this impossible to do, or is another issue causing this stange
>>>> behaviour?
>>>>
>>>> best regards,
>>>> Marko
>>>>
>>>>
>>>> _______________________________________________
>>>> Zope maillist  -  Zope@...
>>>> https://mail.zope.org/mailman/listinfo/zope
>>>> **   No cross posts or HTML encoding!  **
>>>> (Related lists -  https://mail.zope.org/mailman/listinfo/zope-announce
>>>>  https://mail.zope.org/mailman/listinfo/zope-dev )
>>>>
>>>>
>>>>
>>
>>

--

OKTOBER



WIBAUTSTRAAT 122
1091 GP AMSTERDAM



POSTBUS 93121
1090 BC AMSTERDAM

	 T +3120 462 60 60
F +3120 462 60 20  WWW.OKTOBER.NL
INFO@...

_______________________________________________
Zope maillist  -  Zope@...
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope-dev )

I ported an older internal Formulator version (can't remember the version)
to Zope 2.11 which is now working in production.

-aj

Am 16.11.09 03:09, schrieb Remy Pinsonnault:
> I have the same problem, anybody has Formulator working on modern Zope
> version?
>
> On Fri, Jul 3, 2009 at 6:56 AM, Andreas Jung <lists@...
> <mailto:lists@...>> wrote:
>
>     We have a project where we are using Formulator under CMF 1.X +
>     Zope 2.8.
>     Unfortunately Formulator seems to horribly broken Zope 2.11.
>     Has anyone worked on making Formulator working with some modern
>     Zope/CMF
>     version?
>
>     Andreas
>
>     --
>     ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
>     Web: www.zopyx.com <http://www.zopyx.com> - Email: info@...
>     <mailto:info@...> - Phone +49 - 7071 - 793376
>     Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535
>     Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK
>     ------------------------------------------------------------------------
>     E-Publishing, Python, Zope & Plone development, Consulting
>
>
>
>     _______________________________________________
>     Zope maillist  -  Zope@... <mailto:Zope@...>
>     http://mail.zope.org/mailman/listinfo/zope
>     **   No cross posts or HTML encoding!  **
>     (Related lists -
>      http://mail.zope.org/mailman/listinfo/zope-announce
>      http://mail.zope.org/mailman/listinfo/zope-dev )
>
>


--
ZOPYX Ltd. & Co KG          \  zopyx group
Charlottenstr. 37/1          \  The full-service network for your
D-72070 Tübingen              \  Python, Zope and Plone projects
www.zopyx.com, info@...  \  www.zopyxgroup.com
------------------------------------------------------------------------
E-Publishing, Python, Zope & Plone development, Consulting

_______________________________________________
Zope maillist  -  Zope@...
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope-dev )

_______________________________________________
Zope maillist  -  Zope@...
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope-dev )

And some did lose their blood
http://hikewapubi.servetown.com/aqogoj.html

Anyone willing to make a new release of zope.component and zope.sendmmail,
or give me the pypi access to do it?

Thanks,
Fabio

* 2009-11-08 13:35, Fabio Tranchitella wrote:
> * 2009-11-06 20:34, Fabio Tranchitella wrote:
> > I'm going to merge the code on Sunday, if nobody objects.
>
> I merged the branch back to zope.component and fixed zope.sendmail, which
> was importing a security-related symbol from zope.component.zcml; I ran the
> ZTK tests and I have no failures.
>
> The only missing thing is to release the new versions of zope.component and
> zope.sendmail and (maybe) update the ZTK KGS. I don't have the permissions
> to do the release, though.
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Summary of messages to the zope-tests list.
Period Sat Nov 14 12:00:00 2009 UTC to Sun Nov 15 12:00:00 2009 UTC.
There were 6 messages: 6 from Zope Tests.


Tests passed OK
---------------

Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Sat Nov 14 20:39:14 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013017.html

Subject: OK : Zope-2.11 Python-2.4.6 : Linux
From: Zope Tests
Date: Sat Nov 14 20:41:14 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013018.html

Subject: OK : Zope-2.12 Python-2.6.4 : Linux
From: Zope Tests
Date: Sat Nov 14 20:43:14 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013019.html

Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux
From: Zope Tests
Date: Sat Nov 14 20:45:14 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013020.html

Subject: OK : Zope-trunk Python-2.6.4 : Linux
From: Zope Tests
Date: Sat Nov 14 20:47:14 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013021.html

Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux
From: Zope Tests
Date: Sat Nov 14 20:49:14 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013022.html

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

You jump - I jump - a stupid oath
http://savillllewellyn45410.blogspot.com

Do you have the ZODB mount point set up and pointing to your session_folder?

Marko Kruijer wrote:
> That's not my problem, the session is in it's own .fs file, and it is
> persistent.
> The problem is that the two zope clients use different sessions id's
> for the same user, that's not supposed to happen imo.
>
> Allen Schmidt Sr. wrote:
>> What we did was create a Session.fs and added to the zope and zeo
>> conf files. Then after restarting the zopes and zeo, in the ZMI,
>> create a ZODB mount point and it should see the Session.fs and build
>> the parts in the root of the ZMI that you need. Been a long time but
>> I think those are the steps. That way the session data is its own
>> data.fs file and is persistent across zopes and restarts, etc. The
>> problem is that it IS a data.fs file and therefore an undoing
>> storage. You will have to pack it the same as your main data file.
>> Not a big deal for us as its not used much. Just pack back a couple
>> days so you don't whip any session data that could be going on at
>> that moment.
>>
>> Anyone please chime in if I am missing something. Just taking a shot
>> at an answer based on our set up.
>> Your mileage may vary.
>>
>> Allen
>>
>>
>> Marko Kruijer wrote:
>>> I'm maintaining a ZEO cluster setup that currently consists of 2
>>> Zope clients and 1 ZEO server (Zope version is 2.10.5.)
>>>
>>> I'm using sessions on the hosted site and am having trouble sharing
>>> them across the 2 servers.
>>>
>>> I've done a config as described here:
>>> http://www.zopelabs.com/cookbook/1061234337
>>>
>>> Everything runs fine, except my sessions 'change' randomly. For
>>> example if I output my SESSION data I notice that the sessions ID is
>>> not persistent over i.e. 10 page loads.
>>> The contents of the sessions also change, of course.
>>>
>>> Am I missing something here? The central storage of the sessions
>>> should fix this if i'm correct, but it doesn't.
>>> Is this impossible to do, or is another issue causing this stange
>>> behaviour?
>>>
>>> best regards,
>>> Marko
>>>
>>>
>>> _______________________________________________
>>> Zope maillist  -  Zope@...
>>> https://mail.zope.org/mailman/listinfo/zope
>>> **   No cross posts or HTML encoding!  **
>>> (Related lists -  https://mail.zope.org/mailman/listinfo/zope-announce
>>>  https://mail.zope.org/mailman/listinfo/zope-dev )
>>>
>>>
>>>
>
>
_______________________________________________
Zope maillist  -  Zope@...
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope-dev )

That's not my problem, the session is in it's own .fs file, and it is
persistent.
The problem is that the two zope clients use different sessions id's for
the same user, that's not supposed to happen imo.

Allen Schmidt Sr. wrote:
> What we did was create a Session.fs and added to the zope and zeo conf
> files. Then after restarting the zopes and zeo, in the ZMI, create a
> ZODB mount point and it should see the Session.fs and build the parts
> in the root of the ZMI that you need. Been a long time but I think
> those are the steps. That way the session data is its own data.fs file
> and is persistent across zopes and restarts, etc. The problem is that
> it IS a data.fs file and therefore an undoing storage. You will have
> to pack it the same as your main data file. Not a big deal for us as
> its not used much. Just pack back a couple days so you don't whip any
> session data that could be going on at that moment.
>
> Anyone please chime in if I am missing something. Just taking a shot
> at an answer based on our set up.
> Your mileage may vary.
>
> Allen
>
>
> Marko Kruijer wrote:
>> I'm maintaining a ZEO cluster setup that currently consists of 2 Zope
>> clients and 1 ZEO server (Zope version is 2.10.5.)
>>
>> I'm using sessions on the hosted site and am having trouble sharing
>> them across the 2 servers.
>>
>> I've done a config as described here:
>> http://www.zopelabs.com/cookbook/1061234337
>>
>> Everything runs fine, except my sessions 'change' randomly. For
>> example if I output my SESSION data I notice that the sessions ID is
>> not persistent over i.e. 10 page loads.
>> The contents of the sessions also change, of course.
>>
>> Am I missing something here? The central storage of the sessions
>> should fix this if i'm correct, but it doesn't.
>> Is this impossible to do, or is another issue causing this stange
>> behaviour?
>>
>> best regards,
>> Marko
>>
>>
>> _______________________________________________
>> Zope maillist  -  Zope@...
>> https://mail.zope.org/mailman/listinfo/zope
>> **   No cross posts or HTML encoding!  **
>> (Related lists -  https://mail.zope.org/mailman/listinfo/zope-announce
>>  https://mail.zope.org/mailman/listinfo/zope-dev )
>>
>>
>>
_______________________________________________
Zope maillist  -  Zope@...
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope-dev )

hello friends
VERY VERY new to ZOPE and facing a problem with my final year project :
working on a project that involves making an existing plone product
json rpc enabled so that i can use it for cross site calls from a
Mozilla extension
i cant make standard httprequests because of the cross site security
issues in the browser
the query library (that i have to make json rpc enabled ) works fine
with xml rpc in python and using the GET method in the url but i need
it to work for json requests

i have added this http://www.zope.org/Members/ree/jsonserver2 and
tried using several javascript json rpc libraries but still no luck
are there any settings involved that i have to do to make the query
library json enabled

there is also an examples section to it which breaks the ZMI completely
in the above package there is a test folder containing a test script
to check the working but no clue how to execute it cos in the zmi it
goes into a loop asking for authorization

if u can pls help me and tell me a solution to this problem it will be
just awesome

thanks
jayakrishnan Nair
_______________________________________________
Zope maillist  -  Zope@...
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope-dev )

What we did was create a Session.fs and added to the zope and zeo conf
files. Then after restarting the zopes and zeo, in the ZMI, create a
ZODB mount point and it should see the Session.fs and build the parts in
the root of the ZMI that you need. Been a long time but I think those
are the steps. That way the session data is its own data.fs file and is
persistent across zopes and restarts, etc. The problem is that it IS a
data.fs file and therefore an undoing storage. You will have to pack it
the same as your main data file. Not a big deal for us as its not used
much. Just pack back a couple days so you don't whip any session data
that could be going on at that moment.

Anyone please chime in if I am missing something. Just taking a shot at
an answer based on our set up.
Your mileage may vary.

Allen


Marko Kruijer wrote:
> I'm maintaining a ZEO cluster setup that currently consists of 2 Zope
> clients and 1 ZEO server (Zope version is 2.10.5.)
>
> I'm using sessions on the hosted site and am having trouble sharing them
> across the 2 servers.
>
> I've done a config as described here:
> http://www.zopelabs.com/cookbook/1061234337
>
> Everything runs fine, except my sessions 'change' randomly. For example
> if I output my SESSION data I notice that the sessions ID is not
> persistent over i.e. 10 page loads.
> The contents of the sessions also change, of course.
>
> Am I missing something here? The central storage of the sessions should
> fix this if i'm correct, but it doesn't.
> Is this impossible to do, or is another issue causing this stange behaviour?
>
> best regards,
> Marko
>
>
> _______________________________________________
> Zope maillist  -  Zope@...
> https://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  https://mail.zope.org/mailman/listinfo/zope-announce
>  https://mail.zope.org/mailman/listinfo/zope-dev )
>
>
>
_______________________________________________
Zope maillist  -  Zope@...
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope-dev )

Hi All,

Apologies for the cross post, but I'm not sure this has received the
publicity it deserves...

PyPI grew a commenting and rating system a while back, apparently in
response to requests from users. However, since it's been rolled out,
there's been a backlash from package maintainers who already have
mailing lists, bug trackers, etc for their packages and don't want to
have to try and keep track of yet another support forum.

The arguments for and against are listed here:

http://wiki.python.org/moin/PyPIComments

To resolve the future of the commenting and rating system, a vote has
been set up so everyone can have their say.

To vote, please log in to:

http://pypi.python.org/pypi

...and follow the instructions you'll be presented with.

I would like to remain neutral on this, and for me that means giving
package authors the ability to choose whether they want to receive
comments, ratings or neither rather than either forcing package authors
to accept comments and ratings or abandoning the idea of comments and
ratings completely.

The closest option to that is:

"Allow package owners to disallow comments (ratings unmodified)"

I hope the majority of you feel the same way...

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Summary of messages to the zope-tests list.
Period Thu Nov 12 12:00:00 2009 UTC to Fri Nov 13 12:00:00 2009 UTC.
There were 6 messages: 6 from Zope Tests.


Tests passed OK
---------------

Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Thu Nov 12 20:38:56 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013005.html

Subject: OK : Zope-2.11 Python-2.4.6 : Linux
From: Zope Tests
Date: Thu Nov 12 20:40:56 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013006.html

Subject: OK : Zope-2.12 Python-2.6.4 : Linux
From: Zope Tests
Date: Thu Nov 12 20:42:56 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013007.html

Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux
From: Zope Tests
Date: Thu Nov 12 20:44:56 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013008.html

Subject: OK : Zope-trunk Python-2.6.4 : Linux
From: Zope Tests
Date: Thu Nov 12 20:46:56 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013009.html

Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux
From: Zope Tests
Date: Thu Nov 12 20:48:56 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013010.html

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

I'm maintaining a ZEO cluster setup that currently consists of 2 Zope
clients and 1 ZEO server (Zope version is 2.10.5.)

I'm using sessions on the hosted site and am having trouble sharing them
across the 2 servers.

I've done a config as described here:
http://www.zopelabs.com/cookbook/1061234337

Everything runs fine, except my sessions 'change' randomly. For example
if I output my SESSION data I notice that the sessions ID is not
persistent over i.e. 10 page loads.
The contents of the sessions also change, of course.

Am I missing something here? The central storage of the sessions should
fix this if i'm correct, but it doesn't.
Is this impossible to do, or is another issue causing this stange behaviour?

best regards,
Marko


_______________________________________________
Zope maillist  -  Zope@...
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope-dev )

On Thu, Nov 12, 2009 at 12:29, Martin Aspeli <optilude+lists@...> wrote:
> Leonardo Rochael Almeida wrote:
>> Wouldn't it be better to just move IPubFailure before the abort? [...]
>> I can see the usefulness of the
>> transaction being already doom()ed before this event, but not aborted.
>
> There is an IPubSuccess which runs after the transaction is closed.
> Doing post-processing after closure may be useful to keep transactions
> shorter and thus reduce the risk of conflict errors. I don't think an
> extra event will cost us much, so being consistent and granular is
> probably best.

Fair enough. I still suggest doom()ing the transaction before this event.
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Summary of messages to the zope-tests list.
Period Wed Nov 11 12:00:00 2009 UTC to Thu Nov 12 12:00:00 2009 UTC.
There were 7 messages: 1 from Carlos.Solis, 6 from Zope Tests.


Unknown
-------

Subject: Automated Acceptance Test
From: Carlos.Solis
Date: Wed Nov 11 12:37:04 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012998.html


Tests passed OK
---------------

Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Wed Nov 11 20:39:01 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012999.html

Subject: OK : Zope-2.11 Python-2.4.6 : Linux
From: Zope Tests
Date: Wed Nov 11 20:41:01 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013000.html

Subject: OK : Zope-2.12 Python-2.6.2 : Linux
From: Zope Tests
Date: Wed Nov 11 20:43:01 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013001.html

Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux
From: Zope Tests
Date: Wed Nov 11 20:45:01 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013002.html

Subject: OK : Zope-trunk Python-2.6.2 : Linux
From: Zope Tests
Date: Wed Nov 11 20:47:01 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013003.html

Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux
From: Zope Tests
Date: Wed Nov 11 20:49:01 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013004.html

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Leonardo Rochael Almeida wrote:
> Wouldn't it be better to just move IPubFailure before the abort? Is
> there a reason for subscribing to such an event which would required
> the transaction to be aborted already? I can see the usefulness of the
> transaction being already doom()ed before this event, but not aborted.

There is an IPubSuccess which runs after the transaction is closed.
Doing post-processing after closure may be useful to keep transactions
shorter and thus reduce the risk of conflict errors. I don't think an
extra event will cost us much, so being consistent and granular is
probably best.

Martin

--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Wouldn't it be better to just move IPubFailure before the abort? Is
there a reason for subscribing to such an event which would required
the transaction to be aborted already? I can see the usefulness of the
transaction being already doom()ed before this event, but not aborted.

On Wed, Nov 11, 2009 at 08:53, Martin Aspeli <optilude+lists@...> wrote:
> Hi,
>
> In Zope 2.12 ZPublisher we have a good set of events now, which provide
> useful hooks for modifying the response before or after publication.
> However, I'd like to add one more. ;-)
>
> Basically, we have IPubFailure, but this is sent *after*
> transaction.abort() and endInteraction(). This means that it's
> impossible to read from the ZODB when trying to deal with a failure.
>
> I'd like to add an event before that, IPubBeforeAbort, which mirrors
> IPubBeforeCommit in being sent before the transaction is aborted.
>
> I can do this on Zope trunk + 2.12 branch if no-one objects.
>
> Martin
>
> --
> Author of `Professional Plone Development`, a book for developers who
> want to work with Plone. See http://martinaspeli.net/plone-book
>
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev@...
> https://mail.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -
>  https://mail.zope.org/mailman/listinfo/zope-announce
>  https://mail.zope.org/mailman/listinfo/zope )
>
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

You may have more luck on zope-dev (cc'd). :-)

Stefan


On 11.11.2009, at 18:37, Carlos.Solis wrote:

> Dear all,
>
>
>
> I’m trying to find an open source project that in the current
> version uses automated acceptance tests, but that in previous
> versions it did not. I think that this is the case between Zope 3
> and Zope 2, but I’m not sure. I would like to know if
> Zope.testbrowser was used for automated acceptance test in the
> creation of Zope 3. In addition, I would like to know if this was
> included in the evolution of Zope 2 that use Zope 3 technology.
>
>
>
> Best regards
>
> Carlos Solis
>

--
Stefan H. Holek
stefan@...




_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Summary of messages to the zope-tests list.
Period Tue Nov 10 12:00:00 2009 UTC to Wed Nov 11 12:00:00 2009 UTC.
There were 6 messages: 6 from Zope Tests.


Tests passed OK
---------------

Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Tue Nov 10 20:38:35 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012992.html

Subject: OK : Zope-2.11 Python-2.4.6 : Linux
From: Zope Tests
Date: Tue Nov 10 20:40:35 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012993.html

Subject: OK : Zope-2.12 Python-2.6.2 : Linux
From: Zope Tests
Date: Tue Nov 10 20:42:35 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012994.html

Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux
From: Zope Tests
Date: Tue Nov 10 20:44:35 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012995.html

Subject: OK : Zope-trunk Python-2.6.2 : Linux
From: Zope Tests
Date: Tue Nov 10 20:46:35 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012996.html

Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux
From: Zope Tests
Date: Tue Nov 10 20:48:35 EST 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-November/012997.html

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Hi,

In Zope 2.12 ZPublisher we have a good set of events now, which provide
useful hooks for modifying the response before or after publication.
However, I'd like to add one more. ;-)

Basically, we have IPubFailure, but this is sent *after*
transaction.abort() and endInteraction(). This means that it's
impossible to read from the ZODB when trying to deal with a failure.

I'd like to add an event before that, IPubBeforeAbort, which mirrors
IPubBeforeCommit in being sent before the transaction is aborted.

I can do this on Zope trunk + 2.12 branch if no-one objects.

Martin

--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )

Reinout van Rees wrote:
> Sounds like you're working on your zeo sync tool? :-)

zeoraid. It's been around for a while now, but it's finally going to see
some action...

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
  https://mail.zope.org/mailman/listinfo/zope-announce
  https://mail.zope.org/mailman/listinfo/zope )