~pythonxy/pythonxy-upstream/blaze-into : changes

~pythonxy/pythonxy-upstream/blaze-into » Changes from revision 523

From Revision 523 to 504

Rev	Summary	Authors	Date
523	Merge pull request #596 from dhirschfeld/detect-integral-dty... Merge pull request #596 from dhirschfeld/detect-integral-dtype Fix detection of integral dtypes	Eddie Hebert	6 years ago
522	BUG: allow other connectables to be passed as the bind param BUG: allow other connectables to be passed as the bind param	Joe Jevnik	6 years ago
521	ENH: Map full range of supported precision values. ENH: Map full range of supported precision values. Postgres maps float(1) through float(24) to real, and float(25) to float(53) to double precision. Map those ranges to float32 and float64, respectively.	Eddie Hebert	6 years ago
520	BUG: Fix reflection Postgres double precision columns. BUG: Fix reflection Postgres double precision columns. A double precision column in a Postrges table, whose dshape specified a dtype of `float64` for that column, would return a decimal dtype. Fix by defining a group of types which are 'precision' types, and check for membership in that before attempting to lookup the typeengine typ in `blaze.backends.sql.revtypes` Without the fix applied the newly added test fails with the following assertion error, when comparing the `discover` of the `bind` with the expected values: ``` @assert_dshape_equal.register(object, object) def _base_case(a, b, path=None, **kwargs): > assert a == b, '%s != %s\n%s' % (a, b, _fmt_path(path)) E AssertionError: decimal[precision=53, scale=None] != float64 E path: _.measure['a'] ``` Also, added `sa.Float` as a precision type, which fixes `sa.Float(precision=24)`; this allows removal of the `xfail` marking in `odo/backends/test/test_sql::test_types`.	Eddie Hebert	6 years ago
519	TST: Mark sa.Float(precision=24) case as xfail. TST: Mark sa.Float(precision=24) case as xfail. Instead of commenting out, mark the failing sa.Float(precision=24) case as xfail.	Eddie Hebert	6 years ago
518	BUG: Fix discover for sa.TIMESTAMP. BUG: Fix discover for sa.TIMESTAMP. `discover` was returning a bytes dtype for the `sa.TIMESTAMP` instead of `datetime_`. That bug was because the SQLAlchemy dialect for MSSQL currently directly imports `sa.TIMESTAMP`, causing a collision in `odo.backends.sql.revtypes`. Fix by 1) creating a subclass of `mssql.TIMESTAMP` to use as the key in `revtypes` so that it does not overwrite `sa.TIMESTAMP` 2) assign that subclass to the mssql dialect's `'TIMESTAMP'` (using `ischema_names`), so that the subclass will be returned by the type engine instead of `mssql.TIMESTAMP`. The added test for the (`sa.TIMESTAMP`, `datetime_`) without the fix applied would result in this error: ``` a = Bytes(), b = DateTime(tz=None), path = ('.measure', "['ts']", '.ty') kwargs = {'check_dim': True, 'check_record_order': True} @assert_dshape_equal.register(object, object) def _base_case(a, b, path=None, **kwargs): > assert a == b, '%s != %s\n%s' % (a, b, _fmt_path(path)) E AssertionError: bytes != datetime E path: _.measure['value'].ty ``` This patch includes checks for the other types besides `sa.TIMESTAMP` for better protection against the general case of failures when using `revtypes` to map SQLAlchemy types to dtypes. Those extra cases exposed an issue with `sa.Float(precision=24)`. That case is commented out to keep the fix of this patch on the `sa.TIMESTAMP` mapping. (I would have used `pytest.param` to mark it xfail, but pytest for this project needs to be upgraded first.) See: https://github.com/blaze/odo/issues/567 https://github.com/blaze/odo/pull/568 https://bitbucket.org/zzzeek/sqlalchemy/issues/4092/type-problem-with-mssqltimestamp https://github.com/blaze/blaze/pull/1656	Eddie Hebert	6 years ago
517	TST: Upgrade pytest to latest. TST: Upgrade pytest to latest. Rerunning the tests with the upgraded pytest produces the same number of passing and xfailed tests. With pytest 3.2.3, 5 warnings are now shown. pytest 3.1.0 changed behavior so that warnings are captured and displayed. https://docs.pytest.org/en/latest/changelog.html#id81 The impetus for upgrading is that in another patch, using `pytest.param` to mark a specific parameter as an xfail would have been useful; `pytest.param` was added in 3.1.0	Eddie Hebert	6 years ago
516	#515 switch to Numeric type #515 switch to Numeric type	Richard Postelnik	6 years ago
515	Fix typo in docs Fix typo in docs	David Lakata	6 years ago
514	updated blaze link updated blaze link	Michael Herman	6 years ago
513	Don't rely on ResultProxy.keys for column names Don't rely on ResultProxy.keys for column names These names can be truncated/translated so won't always map back to the column names	dhirschf	6 years ago
512	Add test for nullable foreign-key Add test for nullable foreign-key	dhirschf	6 years ago
511	Make select_or_selectable_to_frame more robust Make select_or_selectable_to_frame more robust Don't fail if there isn't an exact mapping from sql <--> numpy types Use object dtype instead Fixes #554	dhirschf	6 years ago
510	Allow for nullable foreign-keys Allow for nullable foreign-keys	dhirschf	6 years ago
509	pd.NaTType is removed in pandas 0.20 pd.NaTType is removed in pandas 0.20 In pandas 0.20 there is no longer a "pd.NaTType". Replaced with "type(pd.NaT)"	timcera	6 years ago
508	Added mock to ci-requirements.txt Added mock to ci-requirements.txt	dhirschf	6 years ago
507	Mock urlopen to make tests more robust Mock urlopen to make tests more robust	dhirschf	6 years ago
506	Added IDEs section to gitignore Added IDEs section to gitignore	dhirschf	6 years ago
505	Added comment clarifying the mssql.TIMESTAMP data type Added comment clarifying the mssql.TIMESTAMP data type	dhirschf	6 years ago
504	Add mssql.TIMESTAMP type to revtypes Add mssql.TIMESTAMP type to revtypes	Dave Hirschfeld	6 years ago

Older »