GitXplorerGitXplorer
s

python-code-disasters

public
156 stars
57 forks
2 issues

Commits

List of commits on branch master.
Verified
d8dfd20ced7b3e39c2429439bef4dc4b41fce90c

Merge pull request #9 from lk-geimfari/patch-2

ssobolevn committed 6 years ago
Verified
48dd31d6851f7386ff1ff581082103a3ba991190

Update to fit rules

llk-geimfari committed 6 years ago
Verified
cf1bffd406b98bc1b7ee65fd1660b580bb2f57d8

Merge pull request #8 from lk-geimfari/patch-2

ssobolevn committed 6 years ago
Verified
e3db06150a1bc05196050bae893279e915bb609d

Added super disgusting view

llk-geimfari committed 6 years ago
Verified
844b1d6f9ee0254ebc5e6935586884c19026ff26

Merge pull request #7 from robertpro/master

ssobolevn committed 6 years ago
Unverified
e696992e43f11e04fc5bc85531c5fed0f28cb9ed

Worst try/except in python history ever

rrobertpro committed 6 years ago

README

The README file for this repository.

python-code-disasters

What is it all about?

I am, due to my work, seeing a lot of code written by other developers. Sometimes this code is so bad, that it is worth showing to the outer world.

Privacy is very important. There are two things basically:

  1. Refactor your code to remove anything, that might violate any security requirements, corporate rules or license agreements.
  2. It is not a goal of this project to insult or offend anyone, so, please, remove any brand-names, user marks, __author__ variables and so on.

Save yourself!

Do you want to save yourself and your project from a python code disaster? Then use wemake-python-styleguide which is the strictest python linter in existance. With this tool all your code will be awesome!

Contributing

Feel free to contribute. Before contributing, please, double check the Privacy section. Refactor your code to remove as much as you can to leave just the most valuable parts. I think that submitting a broken code is not an issue for this project. Moreover, formatting the code is also not required. Sometimes it is even better to leave it's formation untouched.

It is generally a good practice to read through your old files and contribute your own code.

It is still not clear to me, how to structure this project.

Keywords

Pythod bad code examples, Python antipatterns