Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #68218
| From | Antoine Pitrou <solipsis@pitrou.net> |
|---|---|
| Subject | Re: which async framework? |
| Date | 2014-03-11 15:57 +0000 |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.8048.1394553484.18130.python-list@python.org> (permalink) |
Chris Withers <chris <at> simplistix.co.uk> writes: > > The protocols are all financial (do we really not have a pure-python FIX > library?!) but none are likely to have existing python implementations. If you are mostly writing protocol implementations (aka parsers and serializers), then you should consider writing them in a way that's framework-agnostic. See as an example: https://pypi.python.org/pypi/obelus/0.1 (if you really want to settle on a single framework and don't mind supporting old Python versions, then I recommend asyncio) Regards Antoine.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: which async framework? Antoine Pitrou <solipsis@pitrou.net> - 2014-03-11 15:57 +0000
csiph-web