On 9 Apr, 10:59 pm, don...@stufft.io wrote:
On Apr 9, 2014, at 6:55 PM, Itamar Turner-Trauring
wrote:
On 04/09/2014 03:48 PM, exar...@twistedmatrix.com wrote:
And that shortcoming could be mitigated by documenting (or even
formally declaring) this dependency more prominently (I see it's in
On Apr 10, 2014, at 6:56 AM, exar...@twistedmatrix.com wrote:
> On 9 Apr, 10:59 pm, don...@stufft.io wrote:
>>
>> On Apr 9, 2014, at 6:55 PM, Itamar Turner-Trauring
>> wrote:
>>> On 04/09/2014 03:48 PM, exar...@twistedmatrix.com wrote:
And that shortcoming could be mitigated by docu
Use
pip install -e .[ssl]
in the dir with the twisted setup.py. Works like a charm.
Dustin
On Thu, Apr 10, 2014 at 7:06 AM, Donald Stufft wrote:
>
> On Apr 10, 2014, at 6:56 AM, exar...@twistedmatrix.com wrote:
>
>> On 9 Apr, 10:59 pm, don...@stufft.io wrote:
>>>
>>> On Apr 9, 2014, at 6:55
Oh whoops, I misread what Jean-Paul said. Yes you can do that, either directly
or in a requirements file.
On Apr 10, 2014, at 8:35 AM, Dustin J. Mitchell wrote:
> Use
>
> pip install -e .[ssl]
>
> in the dir with the twisted setup.py. Works like a charm.
>
> Dustin
>
> On Thu, Apr 10, 201
> The protocols are all financial (do we really not have a pure-python FIX
> library?!) but none are likely to have existing python implementations.
>
> How should I pick between the options? What would people recommend and why?
>
This might be a starting point for the FIX stuff
https://pypi.pyt
