GitXplorerGitXplorer
s

python-code-disasters

public
156 stars
57 forks
2 issues

Commits

List of commits on branch master.
Verified
62a3dcda0b2e0106d69f27617c809ff23f48ec85

Adding my horrendous json decorator code

ffish2000 committed 5 years ago
Verified
fb7deacdb03daa4f04493d2458465e5234776cf8

Update README.md

ssobolevn committed 5 years ago
Verified
f871bf959f24450665399c62b9676f4813291f09

Rename genpassword to genpassword.py

ssobolevn committed 5 years ago
Verified
8c620df5c7b9c8b7979a9266552036f4b1412987

Create genpassword

ssobolevn committed 5 years ago
Verified
7f8c856073e746cb79193df90ba2eb5f2eb144e7

Merge pull request #10 from BenjaminUrquhart/patch-1

ssobolevn committed 6 years ago
Verified
469faf7f026b1d9dd71bf4bdc00880351d1bb65c

First major python project

BBenjaminUrquhart 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