All Projects → rednafi → Pysanity

rednafi / Pysanity

Licence: mit
Opinionated coding guidelines and best practices in Python

Programming Languages

python
139335 projects - #7 most used programming language

Projects that are alternatives of or similar to Pysanity

architecture-guidelines
Project Architecture Guidelines Index
Stars: ✭ 14 (-93.17%)
Mutual labels:  best-practices, guidelines
Write Readable Javascript Code
📖 All about writing maintainable JavaScript
Stars: ✭ 244 (+19.02%)
Mutual labels:  best-practices, guidelines
guides
Dealerdirect guides for getting things done, be a programming role-model, coding in style and being the better colleague.
Stars: ✭ 21 (-89.76%)
Mutual labels:  best-practices, guidelines
clean-code-javascript
🛁 Clean Code-Konzepte adaptiert für JavaScript.
Stars: ✭ 37 (-81.95%)
Mutual labels:  best-practices, guidelines
Ios Handbook
Guidelines and best practices for excellent iOS apps
Stars: ✭ 337 (+64.39%)
Mutual labels:  best-practices, guidelines
Guides
Design and development guides
Stars: ✭ 1,880 (+817.07%)
Mutual labels:  best-practices, guidelines
Project Guidelines
A set of best practices for JavaScript projects
Stars: ✭ 25,952 (+12559.51%)
Mutual labels:  best-practices, guidelines
Programming Guidelines
My personal programming guidelines
Stars: ✭ 170 (-17.07%)
Mutual labels:  best-practices, guidelines
The Rest Architectural Style
An article on the REST architecture style.
Stars: ✭ 168 (-18.05%)
Mutual labels:  best-practices
Front End Performance Checklist
🎮 The only Front-End Performance Checklist that runs faster than the others
Stars: ✭ 13,815 (+6639.02%)
Mutual labels:  guidelines
Architecture
.NET 6, ASP.NET Core 6, Entity Framework Core 6, C# 10, Angular 13, Clean Code, SOLID, DDD.
Stars: ✭ 2,285 (+1014.63%)
Mutual labels:  best-practices
Guidelines.spatie.be
The guidelines used at our company
Stars: ✭ 169 (-17.56%)
Mutual labels:  best-practices
Virgilio
Virgilio is developed and maintained by these awesome people. You can email us virgilio.datascience (at) gmail.com or join the Discord chat.
Stars: ✭ 13,200 (+6339.02%)
Mutual labels:  guidelines
Polaris
Validation of best practices in your Kubernetes clusters
Stars: ✭ 2,397 (+1069.27%)
Mutual labels:  best-practices
Learning Cmake
learning cmake
Stars: ✭ 2,524 (+1131.22%)
Mutual labels:  best-practices
Superwerker
Open-source solution to automate the setup of an AWS Cloud environment with prescriptive best practices.
Stars: ✭ 161 (-21.46%)
Mutual labels:  best-practices
Go Advice
List of advice and tricks for Go ʕ◔ϖ◔ʔ
Stars: ✭ 2,233 (+989.27%)
Mutual labels:  guidelines
Wstg
The Web Security Testing Guide is a comprehensive Open Source guide to testing the security of web applications and web services.
Stars: ✭ 3,873 (+1789.27%)
Mutual labels:  best-practices
Lumen Api Starter
Lumen 8 基础上扩展出的API 启动项目,精心设计的目录结构,规范统一的响应数据格式,Repository 模式架构的最佳实践。
Stars: ✭ 197 (-3.9%)
Mutual labels:  best-practices
Lighthouse Check Action
GitHub Action for running @GoogleChromeLabs Lighthouse audits with all the bells and whistles 🔔 Multiple audits, Slack notifications, and more!
Stars: ✭ 175 (-14.63%)
Mutual labels:  best-practices

````¯¯¯¯\____philosophy____/¯¯¯¯````

__Practicality Beats Purity__ ___Automation Brings Salvation___ ____Abstraction is Chaos, Concealed by Confusion____

 

 

What is this?

This is an ever evolving, battle tested and marginally opinionated python coding guideline that is currently being enforced at my company ShopUp. Primarily, it is an attempt to document some of the implicit lessons and good practices that we have picked up while writing, maintaining and documenting python code in production. You may not agree with all the conventions mentioned here but other than the style guide where everyone has different ideas about how code should be formatted, the conventions mentioned here are almost universally accepted as good practices by the python community. The aim is not to have a strict guideline that is imposed upon every codebase, rather it exists to provide a baseline and reduce unnecessary cognitive overload that arises from disagreements during internal code reviews. The guideline is divided into three major segments.

Styling Guideline: A mashup of simplified pep8, pep257 and a few tools for styling automation

Coding Guideline: Conventions, best practices and design patterns

Documentation Guideline: An attempt to streamline API documentation

 

Read the guideline here.

 

Contribution Instructions

Fork the repo
Go to docs/README.md
Make your edit, push to a new branch & send a pull request
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].