This is a low traffic list about using and developing Eventlet. Look through the archives for some useful information and possible answers to questions.
+
+
There's an IRC channel dedicated to Eventlet: #eventlet on freenode. It's a pretty chill place to hang out!
+
We have Eventlet Google+ Community. Join us, +1, share your ideas, report bugs, find new friends or even new job!
+
-
This is a relatively low-traffic list about using and developing eventlet. Look through the archives for some useful information and possible answers to questions.
-
-
There's an IRC channel dedicated to eventlet: #eventlet on freenode. It's a pretty chill place to hang out!
Both repositories are equal and kept in sync.
+ You can use whichever you fancy for downloading, forking, reporting issues and submitting pull requests.
+
+
Pull request policy
+
+
Test is required
+
One commit is strongly preferred, except for very big changes
+
Commit message should follow the following formula:
+
+subsystem: description of why the change is useful
+
+optional details or links to related issues or websites
+
+ The why part is very important. Diff already says what you have done. But nobody knows why.
+
+
Feel free to append yourself into AUTHORS file, sections Thanks To or Contributors.
+
+
If you don't like these rules, raw patches are more than welcome!
-
We use Mercurial for our source control, hosted by BitBucket. It's easy to branch off the main repository and contribute patches, tests, and documentation back upstream.
This is a simple web “crawler” that fetches a bunch of urls using a coroutine pool. It has as much concurrency (i.e. pages being fetched simultaneously) as coroutines in the pool.
