some additional tip addition

Author: sagarlf

docs/python/general.md

@@ -7,7 +7,7 @@ sidebar_label: General Coding Guidelines
 #### These are the general guidelines to be followed:
 
 * See [tools](tools.md) that can be used in development environment setup to ease your coding process. 
-* Always use `python3` and try to stay above version `3.5`. **Latest stable** is recommended.
+* Always use `python3` and try to stay above version `3.5`. **Latest stable** is always recommended.
 * Indentation should always be **space** and width should always be **4**.
 * File size and functionality:
     - break files into modules if you feel they have multiple functionalities.
@@ -17,10 +17,9 @@ sidebar_label: General Coding Guidelines
     - comprehensions over `map` and loop
     - minimal use of `lambda`, use `operator` module with keyfunctions in `sorted`, `groupby` etc.
     - ternary with `if else` in same line. Donot use `and or` clause. i.e. `value and req_value or default`. 
-    - `classmethod` for multiple way of class initialization
 * Imports:
     - Always `import` specific namespace.
-    - Try to use parent namespace for actions. i.e. `import sys: sys.path` rather that `from sys import path`
+    - Try to use parent namespace for actions. i.e. `import sys: sys.path` or `import sys.path` rather that `from sys import path` 
     - Never use `import *` i.e. `from MODULE import *`
     - use namespace whenever possible. Use `as SOMEOTHERNAMESPACE` for collision of namespace
 * If you are using `else` with loops that has `break`. Just comment `#nobreak` for reference as it is for that usage. See [this](http://python-notes.curiousefficiency.org/en/latest/python_concepts/break_else.html) for some clarity.
@@ -29,20 +28,19 @@ sidebar_label: General Coding Guidelines
             if condition:
                 break
         else: #nobreak
-            ELSE LOGIC
+            WHEN break DOESNOT HAPPEN
 
         while True:
             if condition:
                 break
         else: #nobreak
-            ELSE LOGIC
+            WHEN break DOESNOT HAPPEN
     ```
 * Use `pathlib` for path related use case rather than `os.path`
 * Use `mypy` and type annotation when possible for type safe code.
 * `Docker` can be used for deployment. Use `python` images for [`docker`](https://hub.docker.com/_/python).
 * Use `generators` and `yield` instead of data structures for high streams of data.
 * Use `itertools`, `functools` for utilities and `collections` for data structures.
-* Use `dataclasses` if available. Go for `attrs` library if `dataclass` is not present.
 * Use `is not` and `is` for `None`, `True` and `False` specific check only. If most cases truthy and falsy can be checked with  `if VARNAME:`. 
 * Strings: 
     - Adhere to one quote practice. Double quote is recommended. Python doesnot differentiate between **'** or **"**. This may be controlled by `formatter` used as well.
@@ -57,17 +55,20 @@ sidebar_label: General Coding Guidelines
     - Use [`abc`](https://docs.python.org/3/library/abc.html) if you need abstraction. Mixins are more famous in python due to multiple inheritance.
     - Use `property` setter getter only when you need readonly attributes. `__` variables can be used for some privacy.
     - Use `super` for overrides and parent calls.
+    - Use inbuilt `dataclasses` if available. Go for `attrs` library if `dataclasses` is not present or you require a much richer library.
+    - Use `classmethod` decorator for multiple initialization of classes as well as `staticmethod` where needed.
 * 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.
     - Be very carefult on threads and locks, so always discuss what you are doing as it may not always be optimized.
     - Use `asyncio` for IO bound async flow. This is something new and constantly changing in `python`.
+* Try to use configurations outside python files. Usually they are not git tracked so should be editable by others. Try `settings.py` or `config.py` if you **must**. This cannot be the case for frameworks.
 * Recommended third party modules:
     - For Relational Database:
         + Use `sqlalchemy` [core](https://docs.sqlalchemy.org/en/13/core/) for DB abstraction. This is particularly helpful when doing testing in `sqlite` and some other database for production. Also, for query and parameters consistency.
         + Use `sqlalchemy` [ORM](https://docs.sqlalchemy.org/en/13/orm/) or framework supported **ORM** when using specific framework.
         + Use DBAPI drivers such as `pyodbc`, `sqlite`, `mysqlclient` etc only when you donot want `sqlalchemy` dependency or when you are very performance conscious. While the API will be mostly compatible for this as python has DBAPI specification. Parameters binding and some methods may be incompatible or unavailable. **sqlalchemy core is recommended.**
     - `requests` for http request stuff.
         + `aiohttp` or `httpx` are also good.
-    - `attrs` for data oriented objects and classes design.
+    - `attrs` for data oriented objects and classes design. If you don't want to use `dataclasses`.
     - `pytest` for tests.

docs/python/project_structure.md

@@ -11,9 +11,17 @@ sidebar_label: Project Structure
     - :memo: pyproject.toml (can be requirements.txt and setup.py)
     - :file_folder: docs
         * Your documentation
-    - :file_folder: data
+    - :file_folder: data (**OPTIONAL**)
         * Data for project.
-    - :file_folder: {PROJECT_NAME}
+        
+:::tip
+* This folder structure can be used as well. It will have **src** folder for more descriptive stature. 
+    + :file_folder: src
+        - :file_folder: {PROJECT_NAME}
+
+:::
+*
+    - :file_folder: {PROJECT_NAME} 
         + :file_folder: utils
         + :file_folder: service
         + :file_folder: config
@@ -22,7 +30,7 @@ sidebar_label: Project Structure
         + :memo: conftest.py
     - :memo: LICENSE (**OPTIONAL**)
     - :memo: README (can be `md` or `rst`)
-    - Other configurable from third parties (**OPTIONAL**) such as tox.ini
+    - :file_folder: :memo: Other configurable from third parties (**OPTIONAL**) such as tox.ini
 
 :::note
 + **There can be cases where MVC folder structure as well as framework related folder structure can be used.**