Skip to content

TODO(ian): Move all @staticmethods to a seperate class #112

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

Open
Ianleeclark opened this issue Feb 21, 2016 · 1 comment
Open

TODO(ian): Move all @staticmethods to a seperate class #112

Ianleeclark opened this issue Feb 21, 2016 · 1 comment
Labels
Milestone

Comments

@Ianleeclark
Copy link
Owner

File Location: ./pyg/github.py
Line Number: 88
This message was auto-generated by Pygemony: Github

@Ianleeclark
Copy link
Owner Author

This is definitely going to be done, but instead of moving it to a seperate class, I will probably just move them to utilities.

Reasoning behind this: if a method can be static, why should it belong to the class at all? It serves no purpose to be part of an instance variable other than reducing imports.

@Ianleeclark Ianleeclark modified the milestone: 0.5.0 Apr 22, 2016
@Ianleeclark Ianleeclark mentioned this issue Apr 22, 2016
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant