-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
exar...@twistedmatrix.com wrote:
> On 05:05 pm, mike.lifegu...@gmail.com wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hello,
>>
>> I cannot see how to get whether a nick is voiced/opped currently in a
>> given channel in the twisted
On 05:05 pm, mike.lifegu...@gmail.com wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Hello,
>
>I cannot see how to get whether a nick is voiced/opped currently in a
>given channel in the twisted IRC framework. I see methhods of changing
>modes, but not querying. Can this be easily done?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I cannot see how to get whether a nick is voiced/opped currently in a
given channel in the twisted IRC framework. I see methhods of changing
modes, but not querying. Can this be easily done?
Thanks,
- -Mike
-BEGIN PGP SIGNATURE-
Versio
1. About `t.e.adbapi.Transaction.cursor`: It seems that the only
>read/write attribute on a cursor object is `arraysize`, and it seems
>clunky to mess with `Transaction`'s public interface just for that. How
>about leaving the instance variable as `_cursor` and adding
>`getArraySize`/`setArraySize
sstein...@gmail.com wrote:
> On Dec 7, 2009, at 9:50 AM, Konrads Smelkovs wrote:
>
>> Hi,
>>
>> One project I had a look at had this nice syntactic sugar for async function
>> chaining:
>>
> event_one() | event_two() | event_three()
>> I think this could be an interesting alternative to addCa
On Mon, Dec 7, 2009 at 10:02 AM, sstein...@gmail.com wrote:
> On Dec 7, 2009, at 9:50 AM, Konrads Smelkovs wrote:
>
> > Hi,
> >
> > One project I had a look at had this nice syntactic sugar for async
> function chaining:
> >
> > >>> event_one() | event_two() | event_three()
> >
> > I think this co
On Dec 7, 2009, at 9:50 AM, Konrads Smelkovs wrote:
> Hi,
>
> One project I had a look at had this nice syntactic sugar for async function
> chaining:
>
> >>> event_one() | event_two() | event_three()
>
> I think this could be an interesting alternative to addCallback or yield. I
> propose th
Hi,
One project I had a look at had this nice syntactic sugar for async function
chaining:
>>> event_one() | event_two() | event_three()
I think this could be an interesting alternative to addCallback or yield. I
propose the following syntax
# get deferred with one () and two () chained as call
