> I started working on a PEP last year, but I didn't get very far partly
> because I doubted the desire.
>
> What part do you think is a hard problem? Convincing people to switch to a
> new API? *Defining* the new API doesn't seem very hard to me.
>
I must say that the only time I needed the fun
On 12:34 am, stutzb...@google.com wrote:
On Sat, Feb 12, 2011 at 4:22 PM, wrote:
Do people want to seriously consider deprecating asyncore and adding a
replacement for it to the stdlib?
(Hey, PyCon is coming up. How convenient. :)
The desire is there, but it's a hard problem. There was a
Hello Developers!
I'm one of the organizers of the Portland PSF Sprint. We've been working hard
on our proposal to come up with a strong program for a full day of sprinting in
Portland. The day will mostly focus on porting libraries to Python 3, hacking
on PyPY 2.7 compatibility and testing. It
On Sat, Feb 12, 2011 at 4:22 PM, wrote:
> Do people want to seriously consider deprecating asyncore and adding a
> replacement for it to the stdlib?
>
> (Hey, PyCon is coming up. How convenient. :)
>
The desire is there, but it's a hard problem. There was a similar
discussion before PyCon 200
On 12:13 am, p.f.mo...@gmail.com wrote:
On 12 February 2011 23:10, wrote:
On 10:46 pm, greg.ew...@canterbury.ac.nz wrote:
Antoine Pitrou wrote:
On Sun, 13 Feb 2011 11:19:06 +1300
Greg Ewing wrote:
So maybe it's time to design a new module with a better API
and deprecate the old one?
On 12 February 2011 23:10, wrote:
> On 10:46 pm, greg.ew...@canterbury.ac.nz wrote:
>>
>> Antoine Pitrou wrote:
>>>
>>> On Sun, 13 Feb 2011 11:19:06 +1300
>>> Greg Ewing wrote:
>>
So maybe it's time to design a new module with a better API
and deprecate the old one?
>>>
>>> That's call
On 10:46 pm, greg.ew...@canterbury.ac.nz wrote:
Antoine Pitrou wrote:
On Sun, 13 Feb 2011 11:19:06 +1300
Greg Ewing wrote:
So maybe it's time to design a new module with a better API
and deprecate the old one?
That's called Twisted.
I was thinking of something lighter-weight than that.
Antoine Pitrou wrote:
On Sun, 13 Feb 2011 11:19:06 +1300
Greg Ewing wrote:
So maybe it's time to design a new module with a better API
and deprecate the old one?
That's called Twisted.
I was thinking of something lighter-weight than that.
--
Greg
Nick Coghlan wrote:
Flawed API + popularity = years of fun*
So maybe it's time to design a new module with a better API
and deprecate the old one?
--
Greg
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/pyth
On Sun, 13 Feb 2011 11:19:06 +1300
Greg Ewing wrote:
> Nick Coghlan wrote:
>
> > Flawed API + popularity = years of fun*
>
> So maybe it's time to design a new module with a better API
> and deprecate the old one?
That's called Twisted.
___
Python-D
On Sat, 12 Feb 2011 22:42:41 +0100
Éric Araujo wrote:
> > antoine.pitrou pushed f22bac464e11 to devguide:
> > summary:
> > Comment out the "make patchcheck" advice, since it doesn't work for a
> > non-SVN workflow.
>
> patchcheck should work after
> http://svn.python.org/view?view=rev&revision=
> antoine.pitrou pushed f22bac464e11 to devguide:
> summary:
> Comment out the "make patchcheck" advice, since it doesn't work for a
> non-SVN workflow.
patchcheck should work after
http://svn.python.org/view?view=rev&revision=85767 (from
http://bugs.python.org/issue8999). What specific part of
Hey Yeswanth
Students who get involved with the projects they plan to work with early
have a definite edge over students who don't, so certainly get involved
now. While I would highly encourage you to get involved with python-dev
(core projects are top in line), you may also want to consider 3rd
Hi everyone,
I am planning to apply for Gsoc 2011 for the PSF . I would like to know if
any of you have any ideas which can be implemented this summer. I guess the
gsoc 2011 ideas page has not been put up as yet. So I thought maybe any of
you can suggest some ideas .
Thanks
Yeswanth
__
14 matches
Mail list logo
