Skip to content

__init__ should return None #11

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
Merged
merged 1 commit into from
Apr 24, 2015
Merged

__init__ should return None #11

merged 1 commit into from
Apr 24, 2015

Conversation

arand
Copy link
Contributor

@arand arand commented Apr 22, 2015

init should return None or omitted entirely.

@arand
__init__ should return None
9b586df 
__init__ should return None or omitted entirely.
@lunemec
Copy link
Contributor

lunemec commented Apr 23, 2015

Yes, it actually must return None, if you try to return something, you'll raise exception.

@adewes
Copy link
Member

adewes commented Apr 24, 2015

Thanks @arand, @lunemec seems we fell for our own anti-pattern here :D

adewes added a commit that referenced this pull request Apr 24, 2015
@adewes
Merge pull request #11 from arand/patch-1
232c6ba 
__init__ should return None
@adewes adewes merged commit 232c6ba into quantifiedcode:master Apr 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@arand @lunemec @adewes
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy