On Wed, Jun 29, 2011 at 00:17, Tres Seaver tsea...@palladion.com wrote:
- breaking the historic URLs for no purpose is lame, and would
cause useless pain to people with older installations that rely
on them (Yes, Virginia, there were automated buildouts before
zc.buildout).
True. Can
On 2011-6-29 03:02, Johannes Raggam wrote:
On Tue, 2011-06-28 at 18:17 -0400, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2011 01:28 PM, Johannes Raggam wrote:
there is a different version set on zope.org and launchpad.
on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/29/11 08:51 , Wichert Akkerman wrote:
My question would be: why launchpad? Is anyone expecting launchpad to be
a canonical resource for Zope releases? As far as I know none of our
documentation refers to launchpad for downloads and launchpad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
I kept wondering why Launchpad even came up for Zope2 download
resources. I don't recall a discussion where that was decided. PyPI and
zope.org are still the canonical locations.
Actually PyPI is the only canonical
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/29/11 10:20 , Andreas Jung wrote:
Jens Vagelpohl wrote:
I kept wondering why Launchpad even came up for Zope2 download
resources. I don't recall a discussion where that was decided. PyPI and
zope.org are still the canonical locations.
On Wed, Jun 29, 2011 at 8:51 AM, Wichert Akkerman wich...@wiggy.net wrote:
My question would be: why launchpad? Is anyone expecting launchpad to be
a canonical resource for Zope releases? As far as I know none of our
documentation refers to launchpad for downloads and launchpad has never
been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/29/11 10:34 , Hanno Schlichting wrote:
On Wed, Jun 29, 2011 at 8:51 AM, Wichert Akkerman wich...@wiggy.net wrote:
My question would be: why launchpad? Is anyone expecting launchpad to be
a canonical resource for Zope releases? As far as I know
Hi Gary, or any other zc.async developer,
we use zc.async in one site and I noticed there's a hell of a lot of
write transactions caused by it.
Every 30 seconds there's a zope.minmax.Maximum() by the name of
last_ping stored. It looks like this is coming from
zc.async.queue.DispatcherAgents and
On Wed, Jun 29, 2011 at 7:57 AM, Hanno Schlichting ha...@hannosch.eu wrote:
Ideally I'd like to get avoid storing such information in the ZODB at
all and would much prefer a volatile attribute, a thread local or
something on the filesystem. But maybe I'm missing something here were
this
This is the summary for test reports received on the
zope-tests list between 2011-06-28 00:00:00 UTC and 2011-06-29 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
10 matches
Mail list logo
