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.

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

Output for site_stats() is screwed up #138

Closed
brews opened this issue Jul 24, 2019 · 2 comments · Fixed by #143
Closed

Output for site_stats() is screwed up #138

brews opened this issue Jul 24, 2019 · 2 comments · Fixed by #143
Assignees
Labels
bug Something isn't working
Milestone

Comments

@brews
Copy link
Member

brews commented Jul 24, 2019

Looks like the output for site_stats() is screwed up. This is clearly wrong and in need of a fix.

@brews brews added the bug Something isn't working label Jul 24, 2019
@brews brews added this to the v0.5.0 milestone Jul 24, 2019
@brews brews changed the title Looks like the output for site_stats() is screwed up Output for site_stats() is screwed up Jul 24, 2019
@brews brews self-assigned this Jul 25, 2019
@brews
Copy link
Member Author

brews commented Jul 25, 2019

I've opted to remove site_stats() altogether in the upcoming release. You can get the same statistics by defining a printing (via print()) on an intervals() object). This gives users the most power to define intervals and composites exactly how they like.

Let me know if it creates problems for anyone.

@chguiterman
Copy link
Contributor

Good call -- site_stats was a precursor to intervals and was destined for removal.

@brews brews mentioned this issue Jul 25, 2019
brews added a commit that referenced this issue Jul 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants