some additions to convention

Author: sagarlf

docs/python/exceptions.md

@@ -13,6 +13,6 @@ sidebar_label: Exception Handling
     - Write your custom error only when your error is not described or fulfilled by [internal exceptions](https://docs.python.org/3/library/exceptions.html).
     - Create custom `Exception` class primarily suffixing it with `Error` such as `MyCustomError(Exception)` and use it.
     - Always use `Exception` as your parent class for user defined exceptions. Donot use `BaseException`.
-* Add traceback to you mitigation. i.e. either `logging` or mails. Donot `pass`.
+* Add traceback to your mitigation. i.e. either `logging` or mails. Donot `pass`.
 * The `try` block should be specific to desired exception. Donot use huge code chunk in `try`. Use `else` if needed.
 

docs/python/general.md

@@ -37,6 +37,7 @@ sidebar_label: General Coding Guidelines
     - i.e. `with` statement when supported.
     - Always remember to close on exit. i.e. if you open the file `close` on `finally` or better use `with` or `contextlib.closing`.
 * While `python` is an OOP, you can always choose `functions` and `modules` over `class` if there is only one `object` to be created.
+* Use `property` setter when writing OOP and you need readonly attributes.
 * Use `pdb` as debugger whenever required.
 * Multi-threading can be especially used when we have io bound and network bound multiple operation. Multiprocessing can be used to use multiple cores.
     - Recommended module is `concurrent.futures` in most cases. If lower level API is needed there is always `threading` and `multiprocessing` module.

docs/python/logging.md

@@ -14,7 +14,7 @@ sidebar_label: Logging Convention
     - **ERROR**: errors in programs.
     - **CRITICAL**: blocking issues or immediate attention issues.
 * **ERROR and CRITICAL** levels should be mitigated and informed.
-* `logger` is used for naming single logger. Use `NAME_logger` name for more than one logger when required.
+* `logger` is used for naming single logger object. Use `NAME_logger` name for more than one logger when required.
 * It is singleton and single threaded by default for given name of the logger. Can be [non-blocking](https://docs.python.org/3/howto/logging-cookbook.html#dealing-with-handlers-that-block) if required.
 * [Logging Cookbook](https://docs.python.org/3/howto/logging-cookbook.html) for reference.
 * Always use `exception` method rather than `error` method of `logger` object to log traceback when catching exceptions.