TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

A green threading library with true concurrency for Python

30 点作者 lukes386将近 12 年前

6 条评论

jacob019将近 12 年前
I don't really get what advantage this gives me beyond using gevent. There's still no parallelism. The readme describes it as "A solution to concurrency," but I already get that using gevent. Is it just to improve communication between green threads?
评论 #6226008 未加载
评论 #6225693 未加载
评论 #6226969 未加载
pekk将近 12 年前
Since this is a very new project, it is a good time to suggest that you abide by PEP8 (e.g., no 'waitAll') since this would be widely appreciated, and is not easy to fix later on.
评论 #6225884 未加载
fusiongyro将近 12 年前
&gt; Conpig threads still can only run on one core of a processor.<p>The disillusionment caused by having so many options for non-parallel &quot;concurrency&quot; in Python is, I believe, feeding the high defection rate from Python to Go.
评论 #6225793 未加载
评论 #6226283 未加载
评论 #6227088 未加载
rektide将近 12 年前
The resounding question in my mind is why this, when there is Stackless Python? What&#x27;s better about this greenthreading impl? <a href="http://www.stackless.com/" rel="nofollow">http:&#x2F;&#x2F;www.stackless.com&#x2F;</a>
评论 #6226807 未加载
mietek将近 12 年前
&gt; Conpig threads still can only run on one core of a processor.<p>This isn&#x27;t true concurrency. Scaling to 20 million requests per second over 40 cores on a single machine is true concurrency.
评论 #6226033 未加载
评论 #6226069 未加载
erikb将近 12 年前
Where&#x27;s the library? I see about 50 lines of code that don&#x27;t go far beyond a hello world of Gevent and some strangely written nose tests.