On 15 February 2011 00:45, wrote:
> As far as the difficulties of "finding" the good ideas in Twisted goes,
> there are several people familiar with Twisted already contributing to this
> thread. Between us all, I'm sure we can dig out the insidiously buried
> secrets. As I mentioned before, I'
On Tue, Feb 15, 2011 at 11:09 AM, Daniel Stutzbach wrote:
> If we go with something based on or inspired by Twisted, that solves some
> problems, but creates others. Will users be able to later migrate to using
> Twisted proper? Will the standard library module and Twisted go out of
> sync? Wha
On Tue, Feb 15, 2011 at 10:45 AM, wrote:
> As far as the difficulties of "finding" the good ideas in Twisted goes,
> there are several people familiar with Twisted already contributing to this
> thread. Between us all, I'm sure we can dig out the insidiously buried
> secrets. As I mentioned bef
On Sat, Feb 12, 2011 at 8:20 PM, wrote:
> What part do you think is a hard problem? Convincing people to switch to a
> new API?
>
I think the hard parts is coming up with an API that's simple enough to
learn quickly but powerful enough for to cover most use-cases and cleanly
extendable to cover
On 2/14/2011 5:15 PM, Greg Ewing wrote:
Giampaolo Rodolà wrote:
for me it should also fit one crucial requirement: it
should be *simple* and reflect the simplicity and "taste" of all other
stdlib modules, and to fulfill such a requirement I think Twisted
probably needs to be "adapted" a bit.
On 14 Feb, 10:15 pm, greg.ew...@canterbury.ac.nz wrote:
Giampaolo Rodol� wrote:
for me it should also fit one crucial requirement: it
should be *simple* and reflect the simplicity and "taste" of all other
stdlib modules, and to fulfill such a requirement I think Twisted
probably needs to be "ada
> Done. I hope. This is the first one we (currently) have where more
> than one person is being auto-nosied, so I hope I got the syntax right.
It should be fine:
roundup_tracker=> select * from component_add_as_nosy where nodeid = 25;
linkid | nodeid
+
7641 | 25
12434
Giampaolo Rodolà wrote:
for me it should also fit one crucial requirement: it
should be *simple* and reflect the simplicity and "taste" of all other
stdlib modules, and to fulfill such a requirement I think Twisted
probably needs to be "adapted" a bit.
My thoughts exactly -- from a bird's eye
Giampaolo Rodolà wrote:
> Although I don't use it, it seems that Twisted managed to do this by
> splitting the concepts of "transport" and "protocol" / "application"
> and by using zope.interface.
You might want to look at the ILU core, too, just for ideas. Somewhat
to my surprise, the link htt
On Mon, 14 Feb 2011 00:16:05 +0100, Antoine Pitrou wrote:
> On Sun, 13 Feb 2011 14:47:01 + Alexis Métaireau
> wrote:
> > * Is it possible to automatically be in the noisy list for distutils2'
> > bug reports ?
>
> Someone else with the right knowledge and power will have to do that.
Done.
2011/2/13 Antoine Pitrou :
>
>> It would then be subject to python-dev development policy rather than
>> twisted dev policy (which is even stricter!). Would the twisted devs
>> *really* want that? We could use the same processes we have for
>> "externally maintained" libraries, but they have withou
On Mon, 14 Feb 2011 07:40:00 +0100
Georg Brandl wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On behalf of the Python development team, I'm happy to announce
> the third release candidate of Python 3.2.
>
> Python 3.2 is a continuation of the efforts to improve and stabilize
> the
Le lundi 14 février 2011 à 07:40 +0100, Georg Brandl a écrit :
> On behalf of the Python development team, I'm happy to announce
> the third release candidate of Python 3.2.
Oh, the RC3 changelog is still very long. And sorry, because I
contributed to this long list of changes! I hope that the lis
13 matches
Mail list logo
