> I'll probably port 3148 to Python 2.x after its running happily in
> Python 3.2.
Very good news.
One idea: Once library becomes reliable enough- of course there are
various use cases - but IMHO it perfectly fits the problem domain of
implementing an async DB library on top of it. I suppose th
On 18 Sep 2010, at 09:57, k3xji wrote:
Hi,
Is there any work on porting PEP 3148 back to 2.x series. That is a
wonderful PEP, any many long-running applications are really in need
of some stable library for handling stuff in async way just as
proposed in this PEP.
I'll probably port 3148 to P
k3xji writes:
> Is there any work on porting PEP 3148 back to 2.x series. That is a
> wonderful PEP, any many long-running applications are really in need
> of some stable library for handling stuff in async way just as
> proposed in this PEP.
Better would be to port those applications that woul
Hi,
Is there any work on porting PEP 3148 back to 2.x series. That is a
wonderful PEP, any many long-running applications are really in need
of some stable library for handling stuff in async way just as
proposed in this PEP.
Thanks,
--
http://mail.python.org/mailman/listinfo/python-list
