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.

Sign up for GitHub

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

Jump to bottom

Resolve TODO's in tests #45

Open
chrisdembia opened this issue Mar 20, 2013 · 2 comments
Open

Resolve TODO's in tests #45

chrisdembia opened this issue Mar 20, 2013 · 2 comments
Assignees
@moorepants

Comments

@chrisdembia
Copy link
Owner

No description provided.

@ghost ghost assigned moorepants Jun 15, 2013
@chrisdembia
Copy link
Owner Author

I'll try to work on this too but I wanted to make sure we didn't miss this one simply because we didn't assign it to anyone.

@moorepants
Copy link
Collaborator

I think we can release 1.0 before scipy without full test coverage, but we should have close to full coverage before we submit the journal paper. This has some commentary regarding that: http://carlboettiger.info/2013/06/13/what-I-look-for-in-software-papers.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@moorepants moorepants

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@moorepants @chrisdembia