Skip to content

FIX strike prices > 1k #169

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

femtotrader
Copy link
Contributor

Might fix #168

@femtotrader
Copy link
Contributor Author

Tests fails with Python 2.6.

Any idea ?

@jtkiley
Copy link
Contributor

jtkiley commented Feb 8, 2016

I took a look, but I haven't run into that one before.

This kind of thing is why I filed #160.

@aisthesis
Copy link

Are the tests passing for Python 3.x and 2.7?

The code change looks right to me.

@femtotrader
Copy link
Contributor Author

Change is minimal... maybe I can remove this test. I know it's an odd way to fix a test ;-)
Tests are passing with Python 2.7, 3.3, 3.4, 3.5

@davidastephens
Copy link
Member

Looks good - can you squash?

@femtotrader femtotrader force-pushed the issue168_strike_prices_thousands branch from cc96ccf to b7a41fd Compare February 22, 2016 07:21
@femtotrader
Copy link
Contributor Author

Squashed

femtotrader added a commit that referenced this pull request Feb 25, 2016
@femtotrader femtotrader merged commit 61bb179 into pydata:master Feb 25, 2016
@femtotrader femtotrader deleted the issue168_strike_prices_thousands branch September 8, 2016 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Strike prices > 1k are returned as strings
4 participants