Closed aisthesis closed 8 years ago
I think this is more of an argument for deprecating spread functionality. It seems better to let clients make their own custom spreads of whatever kind and responding as needed to exceptions. In order to get the true value after expiry, you need to get additional data to find parity at close on the expiration date.
Cf. https://github.com/aisthesis/opttrack/blob/master/opttrack/lib/spreads/optspread.py
In tracking calendar spreads, the early expiry option should just go to a 0 value rather than raising an exception.