Re: [Zope3-Users] zc.async in Zope2/Plone
Hi, more reports... :) If you want a Zope 2 instance to run the zc.async dispatcher/worker threads, then it might be better to get the DB that zope is using. In Zope 3, there's an event you can subscribe to to get the DB. Maybe there's something similar in Zope 2 these days? I found that this event it's fired since Zope2.11, but I'm using Zope2.10.6 (actually repoze.zope use this version), so I left this option What I did to run more than 1 client instance, is to set the environment variable ZC_ASYNC_UUID from supervisord.conf for each client instance. This will start one dispatcher per instance, right? is that ok? best regards -- Santiago Videla www.revolucionesweb.com.ar http://www.linkedin.com/in/svidela Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que [EMAIL PROTECTED] [EMAIL PROTECTED] somos. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
On Sep 12, 2008, at 7:16 PM, Santiago Videla wrote: Hi Gary, If you want a Zope 2 instance to run the zc.async dispatcher/worker threads, then it might be better to get the DB that zope is using. In Zope 3, there's an event you can subscribe to to get the DB. Maybe there's something similar in Zope 2 these days? I found it. but I'm not sure if really fire the event at any moment. in my configure.zcml I have: subscriber for=zope.app.appsetup. IDatabaseOpenedEvent handler=.handlers.zcasync_config_handler / the instance starts, but it seems that the handler never run You explained this in the email today. Good to know. That means in 2.11 the zc.async setup might be extremely close to that of Zope 3. Cool! 2008-09-12 02:20:01 ERROR zc.async.events UUID 10c69742-8084-11dd-9853-0016d3094e86 already activated in queue (oid 44148): another process? (To stop poll attempts in this process, set ``zc.async.dispatcher.get().activated = False``. To stop polls permanently, don't start a zc.async.dispatcher!) Maybe you are running your tests while you are running your app instance, and that both of them actually connect to your real live ZEO. Or maybe you are starting a dispatcher yourself, *and* zc.async.ftesting.setUp is starting a dispatcher? (ftesting setUp does start one.) right, and what about running many clients with one ZEO. Many clients with one ZEO server is just fine, as long as they have their own UUID. This newer version of the quickstart, based on trunk, explains the idea (look for the Monte Carlo discussion in the second half). http://svn.zope.org/zc.async/trunk/src/zc/async/QUICKSTART_1_VIRTUALENV.txt?rev=90112view=auto The sphinx-processed version of this file is much easier to read, but I don't want to upload that until I have the release that it describes! I'm getting the same error and I don't understand what to do, this is why I need to get the DB that zope is using? No, you don't have to get the same DB. Just maybe cleaner. Each dispatcher process needs its own UUID, as saved in uuid.txt, as controllable by an environmental variable. If you hunt around, I bet you'll find a uuid.txt, probably in the same directory that you usually start your process. If you read that text, you'll see something like this: afd1e0d0-52e1-11dd-879b-0017f2c49bdd The value above (and this file) is created and used by the zc.async package. It is intended to uniquely identify this software instance when it is used to start a zc.async dispatcher. This allows multiple dispatchers, each in its own software instance, to connect to a single database to do work. In order to decide where to look for this file (or to create it, if necessary), the module looks in ``os.environ['ZC_ASYNC_UUID']`` for a file name. If you are using zdaemon (http://pypi.python.org/pypi/zdaemon) to daemonize your process, you can set this in a zdaemon environment section of your zdaemon.conf. Supervisor (http://supervisord.org/) also provides this functionality. Other similar tools probably do as well. If the ``ZC_ASYNC_UUID`` is not found in the environment, it will use ``os.path.join(os.getgwd(), 'uuid.txt')`` as the file name. To get a new identifier for this software instance, delete this file, restart Python, and import zc.async.instanceuuid. This file will be recreated with a new value. thanks for your help again, and sorry for my ignorance Don't apologize! I've spent a lot of time on docs, but they still are far from what I want. The virtualenv quickstart is good, but I need to finish the grok quickstart I have--and then maybe add a Zope 2.11 quickstart! Thanks Gary ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
On Sep 13, 2008, at 2:43 PM, Santiago Videla wrote: Hi, more reports... :) If you want a Zope 2 instance to run the zc.async dispatcher/worker threads, then it might be better to get the DB that zope is using. In Zope 3, there's an event you can subscribe to to get the DB. Maybe there's something similar in Zope 2 these days? I found that this event it's fired since Zope2.11, but I'm using Zope2.10.6 (actually repoze.zope use this version), so I left this option What I did to run more than 1 client instance, is to set the environment variable ZC_ASYNC_UUID from supervisord.conf for each client instance. oops, I just told you about this in the other email, after having skimmed this one too lightly. :-) This will start one dispatcher per instance, right? is that ok? That's exactly right--exactly the intent. Gary ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
On Sep 12, 2008, at 1:23 AM, Santiago Videla wrote:
Well, after some hours and many buildouts done, I couldn't get this
running.
The best approach I got is like this (using repoze.plone):
1) just run the standard buildout.cfg for repoze.plone
2) add zc.async to the eggs section in the buildout and run again.
It's important to add the egg here, when I added just to the extra-
requirements in the setup.py of my egg, it doesn't work. Something
about IOBTree.family32 it's raised... sorry, I didn't copy the
traceback
3) Here, the instance starts, but tests won't work. I had to edit
the test script, to move down the import of zope.testing. after
that, tests are running. Obviously, running the buildout again, will
overwrite this change
I will try to keep working on this, but I have to move on these days
Understood. It's a good start. Thanks for the report!
Now, a question about the usage of zc.async, I followed the docs in
the QUICKSTART txt
In my egg I have this
__init__.py
=
import ZEO.ClientStorage
import ZODB
import zc.async.configure
storage = ZEO.ClientStorage.ClientStorage(
('127.0.0.1', 8881),
name='zeostorage',
)
db = ZODB.DB(storage, database_name='main')
zc.async.configure.base()
zc.async.configure.start(db, poll_interval=1)
This is reasonable.
This pattern is typical for a stand-alone zc.async instance. This
will run the dispatcher in a thread. The next version (1.5) has an
argument to ``start`` to have the dispatcher run in the main thread,
if you'd prefer.
If you want a Zope 2 instance to run the zc.async dispatcher/worker
threads, then it might be better to get the DB that zope is using. In
Zope 3, there's an event you can subscribe to to get the DB. Maybe
there's something similar in Zope 2 these days?
=
some_handlers.py
=
import zc.async.interfaces
def async_job():
From your use of ``Job`` below, I suspect this takes a single
argument, ``portal``, in the real code.
do something
def some_job(context):
urltool = getToolByName(context, portal_url)
portal = urltool.getPortalObject()
#portal._p_jar give us the connection to the ZODB
queue = zc.async.interfaces.IQueue(portal._p_jar)
This is fine, but I wonder if you have to add the _p_jar...
Maybe for this upcoming version I just added the registration to adapt
a persistent object, in addition to a connection? Not sure offhand,
and I have to run. I'd expect this to not require the _p_jar: ``queue
= zc.async.interfaces.IQueue(portal)``
job = queue.put(zc.async.job.Job(
async_job,
portal.aq_base)
)
If you're not going to do anything further with the job, then you
could just leave out ``job =``, of course.
==
This code it's running and it works, but I'm not sure if it's the
correct usage... Gary?
Looks fine. :-)
If you discover that you are doing the same Zope2-specific (or Plone-
specific) setup/teardown for all your jobs, notice that you can have a
Job subclass that defines setUp and tearDown. See what z3.py does,
for instance.
Last question, when I run my test, I'm getting this error
2008-09-12 02:20:01 ERROR zc.async.events UUID
10c69742-8084-11dd-9853-0016d3094e86 already activated in queue
(oid 44148): another process? (To stop poll attempts in this
process, set ``zc.async.dispatcher.get().activated = False``. To
stop polls permanently, don't start a zc.async.dispatcher!)
Maybe you are running your tests while you are running your app
instance, and that both of them actually connect to your real live ZEO.
Or maybe you are starting a dispatcher yourself, *and*
zc.async.ftesting.setUp is starting a dispatcher? (ftesting setUp
does start one.)
I was reading ftesting.txt from zc.async but I yet don't understand
what should I do, any hints?
best regards
On Thu, Sep 11, 2008 at 5:51 PM, Michael Dunstan [EMAIL PROTECTED]
wrote:
On Fri, Sep 12, 2008 at 5:02 AM, Santiago Videla
[EMAIL PROTECTED] wrote:
Hi guys,
z3c.recipe.fakezope2eggs lets you tame these kind of
dependencies. See
http://pypi.python.org/pypi/z3c.recipe.fakezope2eggs
plone.recipe.zope2install includes a couple of options for
making use
of that too. See http://pypi.python.org/pypi/plone.recipe.zope2install
Nice, I will try those.
But I have another issue... :(
I need to use repoze.plone and I don't have any zope2 section in my
buildout.cfg (needed to use fakezope2eggs). I need to find a way
to tell to
fakezope2eggs where is the python/lib/zope directory
I think you should be able to do that by declaring a zope2-location
for the z3c.recipe.fakezope2eggs part.
[fakezope2eggs]
recipe =
Re: [Zope3-Users] zc.async in Zope2/Plone
Hi Gary, If you want a Zope 2 instance to run the zc.async dispatcher/worker threads, then it might be better to get the DB that zope is using. In Zope 3, there's an event you can subscribe to to get the DB. Maybe there's something similar in Zope 2 these days? I found it. but I'm not sure if really fire the event at any moment. in my configure.zcml I have: subscriber for=zope.app.appsetup.IDatabaseOpenedEvent handler=.handlers.zcasync_config_handler / the instance starts, but it seems that the handler never run 2008-09-12 02:20:01 ERROR zc.async.events UUID 10c69742-8084-11dd-9853-0016d3094e86 already activated in queue (oid 44148): another process? (To stop poll attempts in this process, set ``zc.async.dispatcher.get().activated = False``. To stop polls permanently, don't start a zc.async.dispatcher!) Maybe you are running your tests while you are running your app instance, and that both of them actually connect to your real live ZEO. Or maybe you are starting a dispatcher yourself, *and* zc.async.ftesting.setUp is starting a dispatcher? (ftesting setUp does start one.) right, and what about running many clients with one ZEO. I'm getting the same error and I don't understand what to do, this is why I need to get the DB that zope is using? thanks for your help again, and sorry for my ignorance cheers -- Santiago Videla www.revolucionesweb.com.ar http://www.linkedin.com/in/svidela Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que [EMAIL PROTECTED] [EMAIL PROTECTED] somos. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
Hi guys, z3c.recipe.fakezope2eggs lets you tame these kind of dependencies. See http://pypi.python.org/pypi/z3c.recipe.fakezope2eggs plone.recipe.zope2install includes a couple of options for making use of that too. See http://pypi.python.org/pypi/plone.recipe.zope2install Nice, I will try those. But I have another issue... :( I need to use repoze.plone and I don't have any zope2 section in my buildout.cfg (needed to use fakezope2eggs). I need to find a way to tell to fakezope2eggs where is the python/lib/zope directory It would be great to have an example buildout of a Zope2 instance configured with zc.async. Yes! I'd love to include this in the docs too. Santiago, I won't have a chance to try this in Zope 2 for awhile, but I'd love to help, and to publicize your success. ;-) well, I will do my best. cheers Gary -- Santiago Videla www.revolucionesweb.com.ar http://www.linkedin.com/in/svidela Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que [EMAIL PROTECTED] [EMAIL PROTECTED] somos. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
On Fri, Sep 12, 2008 at 5:02 AM, Santiago Videla [EMAIL PROTECTED] wrote: Hi guys, z3c.recipe.fakezope2eggs lets you tame these kind of dependencies. See http://pypi.python.org/pypi/z3c.recipe.fakezope2eggs plone.recipe.zope2install includes a couple of options for making use of that too. See http://pypi.python.org/pypi/plone.recipe.zope2install Nice, I will try those. But I have another issue... :( I need to use repoze.plone and I don't have any zope2 section in my buildout.cfg (needed to use fakezope2eggs). I need to find a way to tell to fakezope2eggs where is the python/lib/zope directory I think you should be able to do that by declaring a zope2-location for the z3c.recipe.fakezope2eggs part. [fakezope2eggs] recipe = z3c.recipe.fakezope2eggs zope2-location = ... where ... points to your python directory of python/lib/zope -- Michael Dunstan ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
Well, after some hours and many buildouts done, I couldn't get this running.
The best approach I got is like this (using repoze.plone):
1) just run the standard buildout.cfg for repoze.plone
2) add zc.async to the eggs section in the buildout and run again.
It's important to add the egg here, when I added just to the
extra-requirements in the setup.py of my egg, it doesn't work. Something
about IOBTree.family32 it's raised... sorry, I didn't copy the traceback
3) Here, the instance starts, but tests won't work. I had to edit the test
script, to move down the import of zope.testing. after that, tests are
running. Obviously, running the buildout again, will overwrite this change
I will try to keep working on this, but I have to move on these days
Now, a question about the usage of zc.async, I followed the docs in the
QUICKSTART txt
In my egg I have this
__init__.py
=
import ZEO.ClientStorage
import ZODB
import zc.async.configure
storage = ZEO.ClientStorage.ClientStorage(
('127.0.0.1', 8881),
name='zeostorage',
)
db = ZODB.DB(storage, database_name='main')
zc.async.configure.base()
zc.async.configure.start(db, poll_interval=1)
=
some_handlers.py
=
import zc.async.interfaces
def async_job():
do something
def some_job(context):
urltool = getToolByName(context, portal_url)
portal = urltool.getPortalObject()
#portal._p_jar give us the connection to the ZODB
queue = zc.async.interfaces.IQueue(portal._p_jar)
job = queue.put(zc.async.job.Job(
async_job,
portal.aq_base)
)
==
This code it's running and it works, but I'm not sure if it's the correct
usage... Gary?
Last question, when I run my test, I'm getting this error
2008-09-12 02:20:01 ERROR zc.async.events UUID
10c69742-8084-11dd-9853-0016d3094e86 already activated in queue (oid
44148): another process? (To stop poll attempts in this process, set
``zc.async.dispatcher.get().activated = False``. To stop polls permanently,
don't start a zc.async.dispatcher!)
I was reading ftesting.txt from zc.async but I yet don't understand what
should I do, any hints?
best regards
On Thu, Sep 11, 2008 at 5:51 PM, Michael Dunstan
[EMAIL PROTECTED]wrote:
On Fri, Sep 12, 2008 at 5:02 AM, Santiago Videla
[EMAIL PROTECTED] wrote:
Hi guys,
z3c.recipe.fakezope2eggs lets you tame these kind of dependencies. See
http://pypi.python.org/pypi/z3c.recipe.fakezope2eggs
plone.recipe.zope2install includes a couple of options for making use
of that too. See http://pypi.python.org/pypi/plone.recipe.zope2install
Nice, I will try those.
But I have another issue... :(
I need to use repoze.plone and I don't have any zope2 section in my
buildout.cfg (needed to use fakezope2eggs). I need to find a way to tell
to
fakezope2eggs where is the python/lib/zope directory
I think you should be able to do that by declaring a zope2-location
for the z3c.recipe.fakezope2eggs part.
[fakezope2eggs]
recipe = z3c.recipe.fakezope2eggs
zope2-location = ...
where ... points to your python directory of python/lib/zope
--
Michael Dunstan
--
Santiago Videla
www.revolucionesweb.com.ar
http://www.linkedin.com/in/svidela
Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el
pensamiento que se hace corazón resplandece con la palabra sencilla y
humilde que [EMAIL PROTECTED] [EMAIL PROTECTED] somos.
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] zc.async in Zope2/Plone
Hi people, I want to use zc.async in a Zope2/Plone web app. The problem that I found it's that zc.async requires zope.testing. When I run buildout it seems that zope.testing overwrite the testing module from zope2 (instance/lib/python/zope/testing) and when I try to run my automated tests I get an error in testrunner.py about 'other' attribute The questions are: * it's possible to run zc.async over Zope2 ? I think it is, in fact, I have it running (I think), but the tests get broken as I said * How can I solve this problem?? There is any way to say in the buildout.cfg: Ignore the zope.testing package I guess that I won't be able to run the tests for zc.async, but I can live with that... * If I find a way to remove zope.testing, (downloading the source and removing that requirement, I know it's ugly) could that get me into troubles ?? * Could zope.testing be require for something else than tests over zc.async and it's dependecies?? thanks in advance -- Santiago Videla www.revolucionesweb.com.ar http://www.linkedin.com/in/svidela Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que [EMAIL PROTECTED] [EMAIL PROTECTED] somos. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
On Sep 10, 2008, at 2:55 PM, Santiago Videla wrote: Hi people, Hi! I want to use zc.async in a Zope2/Plone web app. The problem that I found it's that zc.async requires zope.testing. When I run buildout it seems that zope.testing overwrite the testing module from zope2 (instance/lib/python/zope/testing) and when I try to run my automated tests I get an error in testrunner.py about 'other' attribute That's a shame. Could it be that, if you specify a version of zope.testing in your setup.py that is equivalent to the version of zope.testing in your Plone app, the overwriting happens but without ill effects? I bet that would work. The questions are: * it's possible to run zc.async over Zope2 ? I sure hope so. I intend it to be. :-) I think it is, in fact, I have it running (I think), yay! but the tests get broken as I said Mm. :-( * How can I solve this problem?? There is any way to say in the buildout.cfg: Ignore the zope.testing package Not at the moment. I have been following the ZC opinion--brought about by pain, not theory, BTW--that test dependencies should be included as primary dependencies. However, your story seems like a reason to divide up the requirements, especially if my first suggestion doesn't work for you. Maybe I'll do that for the next release (1.5.0) which I hope/intend to make in the next 7 days. If that's not soon enough, you could make a local release for yourself, as you mention below, that divides out or removes the requirement. I guess that I won't be able to run the tests for zc.async, but I can live with that... Right. It's a shame and an annoyance, but not necessarily a show- stopper. * If I find a way to remove zope.testing, (downloading the source and removing that requirement, I know it's ugly) could that get me into troubles ?? I don't believe so. Though there are no automated tests to guarantee that, of course. :-) * Could zope.testing be require for something else than tests over zc.async and it's dependecies?? That is not the intent. So, to repeat, I *want* it to work (easily!) in Zope 2/Plone. I think your best solution is to see if you can pin the zope.testing egg to the same version that your Zope 2/Plone app currently uses, and see if it works. If that fails, let me know. Gary ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
Hi Gary thanks for the help That's a shame. Could it be that, if you specify a version of zope.testing in your setup.py that is equivalent to the version of zope.testing in your Plone app, the overwriting happens but without ill effects? I bet that would work. I will have to this with all the packages that zc.async requires, right? zope.component zope.interface zope.testing ... and so on what I don't know is where I can find what versions for each egg should I use. Latest plone use Zope.2.10.6. is there any place where I can see the versions? I found this: http://svn.zope.org/Zope2.buildout/trunk/versions-zope3.cfg?rev=90415view=markup but I'm not sure if it's correct http://www.zope.org/Products/Zope/2.10.6/Zope-2.10.6-released - Zope 3.3, Five 1.5 integration - replaced several Zope 2 modules with their sister implementation of Zope 3 I guess that I have to specify all the versions that Zope3.3 uses Not at the moment. I have been following the ZC opinion--brought about by pain, not theory, BTW--that test dependencies should be included as primary dependencies. However, your story seems like a reason to divide up the requirements, especially if my first suggestion doesn't work for you. Maybe I'll do that for the next release (1.5.0) which I hope/intend to make in the next 7 days. don't worry, others packages requires zope.testing as well * ZODB * zc.twist cheers -- Santiago Videla www.revolucionesweb.com.ar http://www.linkedin.com/in/svidela Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que [EMAIL PROTECTED] [EMAIL PROTECTED] somos. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
On Sep 10, 2008, at 5:01 PM, Santiago Videla wrote: Hi Gary thanks for the help That's a shame. Could it be that, if you specify a version of zope.testing in your setup.py that is equivalent to the version of zope.testing in your Plone app, the overwriting happens but without ill effects? I bet that would work. I will have to this with all the packages that zc.async requires, right? zope.component zope.interface zope.testing ... and so on Well, for a stable production, I believe you'll want to specify all of those, yeah. For your specific problem here, it's less clear. For a first cut, I'd probably aim for the minimum changes that you discover you need, but yeah, another approach would be to specify all of the packages that overlap. I don't know which approach will be faster. what I don't know is where I can find what versions for each egg should I use. Latest plone use Zope.2.10.6. is there any place where I can see the versions? I found this: http://svn.zope.org/Zope2.buildout/trunk/versions-zope3.cfg?rev=90415view=markup but I'm not sure if it's correct http://www.zope.org/Products/Zope/2.10.6/Zope-2.10.6-released • Zope 3.3, Five 1.5 integration • replaced several Zope 2 modules with their sister implementation of Zope 3 I guess that I have to specify all the versions that Zope3.3 uses Zope 3.3 was not eggified. Looking on pypi (http://pypi.python.org/simple/zope.testing) it looks like you can try the 3.6 line, the 3.5 line, the 3.4 line or the 3.0 line. If you don't get success soon, let me know what the exact traceback you get is, and under what exact circumstance (running your own tests, right?). I might be able to suggest a specific zope.testing version. I suspect this won't be as easy as I would like until Zope 2/Plone is eggified. :-/ That said, having to specify versions wouldn't be too bad, once the version cocktail has been determined. Not at the moment. I have been following the ZC opinion--brought about by pain, not theory, BTW--that test dependencies should be included as primary dependencies. However, your story seems like a reason to divide up the requirements, especially if my first suggestion doesn't work for you. Maybe I'll do that for the next release (1.5.0) which I hope/ intend to make in the next 7 days. don't worry, others packages requires zope.testing as well * ZODB * zc.twist I hear you. FWIW, I can help with zc.twist if you want, but I doubt ZODB is going to change. Gary ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
On Thu, Sep 11, 2008 at 6:55 AM, Santiago Videla [EMAIL PROTECTED] wrote: * How can I solve this problem?? There is any way to say in the buildout.cfg: Ignore the zope.testing package I guess that I won't be able to run the tests for zc.async, but I can live with that... z3c.recipe.fakezope2eggs lets you tame these kind of dependencies. See http://pypi.python.org/pypi/z3c.recipe.fakezope2eggs plone.recipe.zope2install includes a couple of options for making use of that too. See http://pypi.python.org/pypi/plone.recipe.zope2install It would be great to have an example buildout of a Zope2 instance configured with zc.async. -- Michael Dunstan ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zc.async in Zope2/Plone
On Sep 10, 2008, at 5:27 PM, Michael Dunstan wrote: On Thu, Sep 11, 2008 at 6:55 AM, Santiago Videla [EMAIL PROTECTED] wrote: * How can I solve this problem?? There is any way to say in the buildout.cfg: Ignore the zope.testing package I guess that I won't be able to run the tests for zc.async, but I can live with that... z3c.recipe.fakezope2eggs lets you tame these kind of dependencies. See http://pypi.python.org/pypi/z3c.recipe.fakezope2eggs plone.recipe.zope2install includes a couple of options for making use of that too. See http://pypi.python.org/pypi/plone.recipe.zope2install Great! It would be great to have an example buildout of a Zope2 instance configured with zc.async. Yes! I'd love to include this in the docs too. Santiago, I won't have a chance to try this in Zope 2 for awhile, but I'd love to help, and to publicize your success. ;-) Gary ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
