Eddie Hebert 3e3d95ebb9 BUG: Fix data.history with a single continuous future. ...

Allow `ContinuousFuture` when checking for a single "asset".

This could be further improved by:

- Defininng a tuple of the `Asset`-like types OR making
`ContinuousFuture` and `Asset` share a common type (whether that is
`ContinuousFuture` inheriting from `Asset` or making `Asset` and
`ContinuousFuture` share a common type.)

- Make a `history` test which uses `BarData` + `ContinuousFuture`,
instead of just using the history loader directly from tests.

2016-11-07 16:34:26 -05:00

..

__init__.py

Revert "Merge pull request #1354 from quantopian/revert-1302-point-in-time-asset-db"

2016-08-02 14:25:10 -04:00

_assets.pyx

ENH: If no exchange_full provided, use exchange

2016-08-19 16:45:52 -04:00

asset_db_migrations.py

MAINT: Put downgrade in transaction

2016-08-24 13:24:07 -04:00

asset_db_schema.py

Revert "Merge pull request #1354 from quantopian/revert-1302-point-in-time-asset-db"

2016-08-02 14:25:10 -04:00

asset_writer.py

MAINT: Use sort_values instead of sort().

2016-09-20 17:12:08 -04:00

assets.py

BUG: Fix data.history with a single continuous future.

2016-11-07 16:34:26 -05:00

continuous_futures.pyx

BUG: Protect against contract offset at end of range. (#1564)

2016-10-27 16:48:34 -04:00

futures.py

MAINT: Remove future_chain API method.

2016-09-21 11:08:34 -04:00

roll_finder.py

ENH: Allow configurable history prefetch length.

2016-11-04 13:30:30 -04:00

synthetic.py

MAINT: Don't use convert_objects().

2016-09-20 17:12:07 -04:00