2009/7/8 Jonathan Lange :
> Hello all,
>
> I've recently returned from EuroPython where I got a chance to work
> with Thomas Hervé on Twisted. In the giddy rush of success I thought,
> "Wouldn't it be great if we could get a whole week to do this?".
>
> I propose that:
> - we arrange a week long s
Steve Steiner (listsin) wrote:
As for the date, it should be no sooner than September 7. As a
starting point, let's say Sep 28-Oct 2.
I'm hoping to be able to come for a day or two -- perhaps work on
testing and/or documentation.
___
Tw
>>> As for the date, it should be no sooner than September 7. As a
>>> starting point, let's say Sep 28-Oct 2.
Works for me, as well. I'm just an hour North in New Hampshire so I'm
pretty flexible around anyone else's schedule.
S
___
Twisted-Pyth
On 9 Jul 2009, at 17:42, Jamu Kakar wrote:
Hi Jono,
On Tue, Jul 7, 2009 at 9:31 PM, Jonathan Lange wrote:
I've recently returned from EuroPython where I got a chance to work
with Thomas Hervé on Twisted. In the giddy rush of success I thought,
"Wouldn't it be great if we could get a whole week
Hi Jono,
On Tue, Jul 7, 2009 at 9:31 PM, Jonathan Lange wrote:
> I've recently returned from EuroPython where I got a chance to work
> with Thomas Hervé on Twisted. In the giddy rush of success I thought,
> "Wouldn't it be great if we could get a whole week to do this?".
Indeed, sprinting is supe
I'm trying to add SSL support to an app that makes use of Perspective
Broker. In my server I have the following:
ccf = ssl.ContextFactory()
ccf.method = SSL.TLSv1_METHOD
reactor.listenSSL(PORT, pb.PBServerFactory(RLFactory()), ccf)
and in my client I have this:
ccf = ssl.ClientContextFactory()
c
On Wed, Jul 8, 2009 at 11:26 PM, wrote:
>> As for the date, it should be no sooner than September 7. As a
>> starting point, let's say Sep 28-Oct 2.
>
> This should be a pretty good time for me, and it's in my calendar now.
> Anyone else going to have problems making it to an end-of-September spri
On Tue, 2009-07-07 at 19:25 -0400, Jean-Paul Calderone wrote:
> I suppose your sudoers configuration file wasn't recognizing the command
> before (since it was indeed a different command) and so wasn't letting you
> go through the no-password case.
Ahh, okay. Between that and Maarten's illuminat
