forked from webpy/webpy
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update the select() to show what it returns, so that the documentatio…
…n is more complete.
- Loading branch information
Showing
1 changed file
with
14 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9fb28c5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should probably a) refer to web.query and put this there, b) write it as an actual doctest.
9fb28c5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've never written a doctest before, I've always done nose/unittest type testing. My understanding is doctests are executable code, but we don't have a DB to execute against I would imagine. I guess I'll have to figure out how you do it for your other tests.
as for webpy#1, you are right about db.query and a reference.