Skip to content
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

follow up on issue #24, code breaks on rogue fields #41

Closed
ms5 opened this issue Jun 13, 2015 · 1 comment
Closed

follow up on issue #24, code breaks on rogue fields #41

ms5 opened this issue Jun 13, 2015 · 1 comment

Comments

@ms5
Copy link
Contributor

ms5 commented Jun 13, 2015

I come back to issue #24 , since with the move to schematics the problem is again here. For example I get the following exception on rogue fields and that breaks the data of that market, so my bot is useless again...

schematics.exceptions.ModelConversionError: {'description': {'each_way_divisor': 'Rogue field'}}

In general I think, there is no need to raise an exception on rogue fields, because the model/bot will continue to work, even if betfair decides to add new data. this new fields can latter be added to the betfair.py model.

@jmcarp
Copy link
Owner

jmcarp commented Jun 15, 2015

Thanks for the fix!

@jmcarp jmcarp closed this as completed Jun 15, 2015
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

No branches or pull requests

2 participants