On Wed, Apr 23, 2008 at 10:48 PM, Paul Carduner [EMAIL PROTECTED] wrote:
On Wed, Apr 23, 2008 at 12:01 PM, Martin Aspeli [EMAIL PROTECTED] wrote:
I would start with the simple HTML approach, personally. It may be all we
need.
Hopefully there will be a first sample of this in the next
Summary of messages to the zope-tests list.
Period Wed Apr 23 11:00:00 2008 UTC to Thu Apr 24 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Wed Apr 23 21:00:36 EDT 2008
URL:
authorize.net has changed their CA for test.authorize.net and attempts
to connect there with zc.authorizedotnet currently fail. The key
that's needed is at the end of this message.
Thanks!
Kevin
-BEGIN CERTIFICATE-
MIIE2DCCBEGgAwIBAgIEN0rSQzANBgkqhkiG9w0BAQUFADCBwzELMAkGA1UEBhMC
Hi,
So, I saw Martijn's paver: buildout is utterly doomed message on
Tuesday, but I haven't had a chance to respond to it until now.
As Kent points out immediately following, I plan to use zc.buildout's
machinery. I actively use zc.buildout now, and I'm looking forward to
getting my
On Wednesday 23 April 2008, Marius Gedminas wrote:
Okay, so I think we should use the KGS and declare the set of packages in
there as Zope 3.4.0.
The KGS changes from time to time, doesn't it? Do you mean the set of
packages frozen at this moment in time?
No, when we do a release, I
On Thu, Apr 24, 2008 at 2:09 AM, Paul Carduner [EMAIL PROTECTED] wrote:
On Wed, Apr 23, 2008 at 10:48 PM, Paul Carduner [EMAIL PROTECTED] wrote:
On Wed, Apr 23, 2008 at 12:01 PM, Martin Aspeli [EMAIL PROTECTED] wrote:
I would start with the simple HTML approach, personally. It may be all
Okay, so I think we should use the KGS and declare the set of packages in
there as Zope 3.4.0.
The KGS changes from time to time, doesn't it? Do you mean the set of
packages frozen at this moment in time?
No, when we do a release, I provide frozen versions of the KGS. See:
Hi Paul. This is beautiful. A recipe is what we need now. Send me a mail
off list if you want some help with this.
Regards,
David
Kent Tenney wrote:
On Thu, Apr 24, 2008 at 2:09 AM, Paul Carduner [EMAIL PROTECTED] wrote:
On Wed, Apr 23, 2008 at 10:48 PM, Paul Carduner [EMAIL PROTECTED]
Hey,
On Thu, Apr 24, 2008 at 5:52 AM, Baiju M [EMAIL PROTECTED] wrote:
[snip]
We will be using Sphinx for the site.
It will require:
1. Python 2.4
2. Sphinx
3. docutils
4. Pygments
Strictly speaking only the person who generates the documentation
would need Sphinx, as I think it
On Apr 24, 2008, at 1:12 AM, Christian Theune wrote:
Hi,
On Wed, Apr 23, 2008 at 04:47:59PM -0400, Jim Fulton wrote:
On Apr 23, 2008, at 4:47 PM, Marius Gedminas wrote:
...
The point of my message was not to whine
about the state of zope.testing, but to present a new argument
against
On Wed, 2008-04-23 at 22:38 +0300, Marius Gedminas wrote:
By the way, the usual way to run tests in the Zope-3-land is to use
bin/test rather than setup.py test. It uses a slightly different test
runner that uses a slightly different method of getting the test
description and therefore hides
Hey,
Kevin Dangoor wrote:
So, I saw Martijn's paver: buildout is utterly doomed message on
Tuesday, but I haven't had a chance to respond to it until now.
I knew you'd find out. :)
As Kent points out immediately following, I plan to use zc.buildout's
machinery. I actively use zc.buildout
All,
My name is Kenneth Miller and I am a student of Electronics
Engineering Technology at the University of Houston. My proposal for
the buildout builder has been selected for the Google Summer of Code
program.
You can read my proposal, a list of general deliverables and a
13 matches
Mail list logo
