{"action":"created","issue":{"url":"https://api.github.com/repos/blaze/blaze/issues/1434","repository_url":"https://api.github.com/repos/blaze/blaze","labels_url":"https://api.github.com/repos/blaze/blaze/issues/1434/labels{/name}","comments_url":"https://api.github.com/repos/blaze/blaze/issues/1434/comments","events_url":"https://api.github.com/repos/blaze/blaze/issues/1434/events","html_url":"https://github.com/blaze/blaze/issues/1434","id":137673685,"number":1434,"title":"consistent behavior of compute on nrows","user":{"login":"pratapvardhan","id":3757165,"avatar_url":"https://avatars.githubusercontent.com/u/3757165?v=3","gravatar_id":"","url":"https://api.github.com/users/pratapvardhan","html_url":"https://github.com/pratapvardhan","followers_url":"https://api.github.com/users/pratapvardhan/followers","following_url":"https://api.github.com/users/pratapvardhan/following{/other_user}","gists_url":"https://api.github.com/users/pratapvardhan/gists{/gist_id}","starred_url":"https://api.github.com/users/pratapvardhan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pratapvardhan/subscriptions","organizations_url":"https://api.github.com/users/pratapvardhan/orgs","repos_url":"https://api.github.com/users/pratapvardhan/repos","events_url":"https://api.github.com/users/pratapvardhan/events{/privacy}","received_events_url":"https://api.github.com/users/pratapvardhan/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-03-01T20:08:16Z","updated_at":"2016-03-02T05:45:48Z","closed_at":"2016-03-02T01:29:59Z","body":"Computing `nrows` expression for csv file and sqlite file gives different `type`. For csv files, type is int ax expected. But, for sqlite (probably for other sql too?) it's a sqlalchemy Select object.\r\n\r\n```python\r\nIn [91]: bz.__version__\r\nOut[91]: '0.9.0'\r\n\r\nIn [92]: data = bz.Data('iris.csv')                     # csv file\r\n\r\nIn [93]: bz.compute(data.nrows)\r\nOut[93]: 150\r\n\r\nIn [94]: type(bz.compute(data.nrows))\r\nOut[94]: int\r\n\r\nIn [95]: data = bz.Data('sqlite:///iris.db::iris')       # sqlite file\r\n\r\nIn [96]: bz.compute(data.nrows)\r\nOut[96]: <sqlalchemy.sql.selectable.Select at 0x1775eb3da0; Select object>\r\n\r\nIn [97]: type(bz.compute(data.nrows))\r\nOut[97]: sqlalchemy.sql.selectable.Select\r\n\r\nIn [98]: data.nrows\r\nOut[98]: 150\r\n```\r\n\r\nas an alternative to `bz.compute`, could probably use `bz.into(int, data.nrows)` instead.\r\n\r\nIs this behavior of `bz.compute` on `data.nrows` expected?"},"comment":{"url":"https://api.github.com/repos/blaze/blaze/issues/comments/191075034","html_url":"https://github.com/blaze/blaze/issues/1434#issuecomment-191075034","issue_url":"https://api.github.com/repos/blaze/blaze/issues/1434","id":191075034,"user":{"login":"postelrich","id":3619876,"avatar_url":"https://avatars.githubusercontent.com/u/3619876?v=3","gravatar_id":"","url":"https://api.github.com/users/postelrich","html_url":"https://github.com/postelrich","followers_url":"https://api.github.com/users/postelrich/followers","following_url":"https://api.github.com/users/postelrich/following{/other_user}","gists_url":"https://api.github.com/users/postelrich/gists{/gist_id}","starred_url":"https://api.github.com/users/postelrich/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/postelrich/subscriptions","organizations_url":"https://api.github.com/users/postelrich/orgs","repos_url":"https://api.github.com/users/postelrich/repos","events_url":"https://api.github.com/users/postelrich/events{/privacy}","received_events_url":"https://api.github.com/users/postelrich/received_events","type":"User","site_admin":false},"created_at":"2016-03-02T05:45:48Z","updated_at":"2016-03-02T05:45:48Z","body":"What is with the networkx error? I don't believe that is a dependency of blaze.  See if you still get an error with a clean environment and fresh a terminal."}}