simplefix
simplefix copied to clipboard
da4089
Simple FIX protocol implementation for Python
A function that takes tag number and tag name as input and stores it as dictionary or any other data type. It can also return tag name when given the...
So now that Python 2.7 is officially unsupported, I'd like to flag a date beyond which simplefix won't commit to support it. In common with a few other projects, I'm...
Changes: * add enums as a move towards typing - includes testing to avoid drift from constants * use constants + enums in `message.py` - hopefully an improvement for non-FIX-wizards...
I am using simplefix version 1.0.14. And it gives me error calling get with the nth parameter. ``` Traceback (most recent call last): File "/usr/local/Cellar/[email protected]/3.9.5/Frameworks/Python.framework/Versions/3.9/lib/python3.9/threading.py", line 954, in _bootstrap_inner self.run()...
hi, maybe we could implement a group parsing object it receive the group tags that exists in a group at construction when __init__ it receive the tag group name (nomdentries)...
I've been thinking about adding a socket connection class to a generic FIX IP, was curious if there's anything in beta for this? If not, I'm happy to fork and...
FIX uses the ASCII SOH character to separate (well, maybe terminate) fields. But for human consumption, these are often replaced with, eg. `|` when logging messages. Add optional support for...
It's very common for FIX log files to be written with one message per line, and a direction (send/recv) and timestamp prior to the message. It'd be nice if `FixParser`...
It'd be nice to have symbolic names available for tag numbers and enum values. These could be snarfed from FTC (5.0sp2, I guess).
There is some reason to return null instead of raising exceptions in parser.get_message ?
