supplier-meesho.webflow 1.0.0

package/GitRepos/isort/docs/configuration/custom_sections_and_ordering.md

@@ -0,0 +1,131 @@
+# Custom Sections and Ordering
+
+isort provides lots of features to enable configuring how it sections imports
+and how it sorts imports within those sections.
+You can change the section order with `sections` option from the default
+of:
+
+```ini
+FUTURE,STDLIB,THIRDPARTY,FIRSTPARTY,LOCALFOLDER
+```
+
+to your preference (if defined, omitting a default section may cause errors):
+
+```ini
+sections=FUTURE,STDLIB,FIRSTPARTY,THIRDPARTY,LOCALFOLDER
+```
+
+You also can define your own sections and their order.
+
+Example:
+
+```ini
+known_django=django
+known_pandas=pandas,numpy
+sections=FUTURE,STDLIB,DJANGO,THIRDPARTY,PANDAS,FIRSTPARTY,LOCALFOLDER
+```
+
+would create two new sections with the specified known modules.
+
+The `no_lines_before` option will prevent the listed sections from being
+split from the previous section by an empty line.
+
+Example:
+
+```ini
+sections=FUTURE,STDLIB,THIRDPARTY,FIRSTPARTY,LOCALFOLDER
+no_lines_before=LOCALFOLDER
+```
+
+would produce a section with both FIRSTPARTY and LOCALFOLDER modules
+combined.
+
+**IMPORTANT NOTE**: It is very important to know when setting `known` sections that the naming
+does not directly map for historical reasons. For custom settings, the only difference is
+capitalization (`known_custom=custom` VS `sections=CUSTOM,...`) for all others reference the
+following mapping:
+
+ - `known_standard_library` : `STANDARD_LIBRARY`
+ - `extra_standard_library` : `STANDARD_LIBRARY` # Like known standard library but appends instead of replacing
+ - `known_future_library` : `FUTURE`
+ - `known_first_party`: `FIRSTPARTY`
+ - `known_third_party`: `THIRDPARTY`
+ - `known_local_folder`: `LOCALFOLDER`
+
+This will likely be changed in isort 6.0.0+ in a backwards compatible way.
+
+
+## Auto-comment import sections
+
+Some projects prefer to have import sections uniquely titled to aid in
+identifying the sections quickly when visually scanning. isort can
+automate this as well. To do this simply set the
+`import_heading_{section_name}` setting for each section you wish to
+have auto commented - to the desired comment.
+
+For Example:
+
+```ini
+import_heading_stdlib=Standard Library
+import_heading_firstparty=My Stuff
+```
+
+Would lead to output looking like the following:
+
+```python
+# Standard Library
+import os
+import sys
+
+import django.settings
+
+# My Stuff
+import myproject.test
+```
+
+## Ordering by import length
+
+isort also makes it easy to sort your imports by length, simply by
+setting the `length_sort` option to `True`. This will result in the
+following output style:
+
+```python
+from evn.util import (
+    Pool,
+    Dict,
+    Options,
+    Constant,
+    DecayDict,
+    UnexpectedCodePath,
+)
+```
+
+It is also possible to opt-in to sorting imports by length for only
+specific sections by using `length_sort_` followed by the section name
+as a configuration item, e.g.:
+
+    length_sort_stdlib=1
+
+## Controlling how isort sections `from` imports
+
+By default isort places straight (`import y`) imports above from imports (`from x import y`):
+
+```python
+import b
+from a import a  # This will always appear below because it is a from import.
+```
+
+However, if you prefer to keep strict alphabetical sorting you can set [force sort within sections](https://pycqa.github.io/isort/docs/configuration/options/#force-sort-within-sections) to true. Resulting in:
+
+
+```python
+from a import a  # This will now appear at top because a appears in the alphabet before b
+import b
+```
+
+You can even tell isort to always place from imports on top, instead of the default of placing them on bottom, using [from first](https://pycqa.github.io/isort/docs/configuration/options/#from-first).
+
+```python
+from b import b # If from first is set to True, all from imports will be placed before non-from imports.
+import a
+```

package/GitRepos/isort/docs/configuration/git_hook.md

@@ -0,0 +1,34 @@
+# Git Hook
+
+isort provides a hook function that can be integrated into your Git
+pre-commit script to check Python code before committing.
+
+To cause the commit to fail if there are isort errors (strict mode),
+include the following in `.git/hooks/pre-commit`:
+
+```python
+#!/usr/bin/env python
+import sys
+from isort.hooks import git_hook
+
+sys.exit(git_hook(strict=True, modify=True, lazy=True, settings_file=""))
+```
+
+If you just want to display warnings, but allow the commit to happen
+anyway, call `git_hook` without the strict parameter. If you want to
+display warnings, but not also fix the code, call `git_hook` without the
+modify parameter.
+The `lazy` argument is to support users who are "lazy" to add files
+individually to the index and tend to use `git commit -a` instead.
+Set it to `True` to ensure all tracked files are properly isorted,
+leave it out or set it to `False` to check only files added to your
+index.
+
+If you want to use a specific configuration file for the hook, you can pass its
+path to settings_file. If no path is specifically requested, `git_hook` will
+search for the configuration file starting at the directory containing the first
+staged file, as per `git diff-index` ordering, and going upward in the directory
+structure until a valid configuration file is found or
+[`MAX_CONFIG_SEARCH_DEPTH`](src/config.py:35) directories are checked.
+The settings_file parameter is used to support users who keep their configuration
+file in a directory that might not be a parent of all the other files.

package/GitRepos/isort/docs/configuration/github_action.md

@@ -0,0 +1,63 @@
+# Github Action
+
+isort provides an official [Github Action][github-action-docs] that can be used as part of a CI/CD workflow to ensure a project's imports are properly sorted.
+The action can be found on the [Github Actions Marketplace][python-isort].
+
+## Usage
+
+The `python-isort` plugin is designed to be run in combination with the [`checkout`][checkout-action] and [`setup-python`][setup-python] actions.
+By default, it will run recursively from the root of the repository being linted and will exit with an error if the code is not properly sorted.
+
+### Inputs
+
+#### `isortVersion`
+
+Optional. Version of `isort` to use. Defaults to latest version of `isort`.
+
+#### `sortPaths`
+
+Optional. List of paths to sort, relative to your project root. Defaults to `.`
+
+#### `configuration`
+
+Optional. `isort` configuration options to pass to the `isort` CLI. Defaults to `--check-only --diff`.
+
+#### `requirementsFiles`
+
+Optional. Paths to python requirements files to install before running isort.
+If multiple requirements files are provided, they should be separated by a space.
+If custom package installation is required, dependencies should be installed in a separate step before using this action.
+
+!!! tip
+    It is important that the project's dependencies be installed before running isort so that third-party libraries are properly sorted.
+
+### Outputs
+
+#### `isort-result`
+
+Output of the `isort` CLI.
+
+### Example usage
+
+```yaml
+name: Run isort
+on:
+  - push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-python@v2
+        with:
+          python-version: 3.8
+      - uses: jamescurtin/isort-action@master
+        with:
+            requirementsFiles: "requirements.txt requirements-test.txt"
+```
+
+[github-action-docs]: https://docs.github.com/en/free-pro-team@latest/actions
+[python-isort]: https://github.com/marketplace/actions/python-isort
+[checkout-action]: https://github.com/actions/checkout
+[setup-python]: https://github.com/actions/setup-python

package/GitRepos/isort/docs/configuration/multi_line_output_modes.md

@@ -0,0 +1,121 @@
+# Multi Line Output Modes
+
+This [config option](https://pycqa.github.io/isort/docs/configuration/options/#multi-line-output) defines how from imports wrap when they extend past the line\_length
+limit and has 12 possible settings:
+
+## 0 - Grid
+
+```python
+from third_party import (lib1, lib2, lib3,
+                         lib4, lib5, ...)
+```
+
+## 1 - Vertical
+
+```python
+from third_party import (lib1,
+                         lib2,
+                         lib3
+                         lib4,
+                         lib5,
+                         ...)
+```
+
+## 2 - Hanging Indent
+
+```python
+from third_party import \
+    lib1, lib2, lib3, \
+    lib4, lib5, lib6
+```
+
+## 3 - Vertical Hanging Indent
+
+```python
+from third_party import (
+    lib1,
+    lib2,
+    lib3,
+    lib4,
+)
+```
+
+## 4 - Hanging Grid
+
+```python
+from third_party import (
+    lib1, lib2, lib3, lib4,
+    lib5, ...)
+```
+
+## 5 - Hanging Grid Grouped
+
+```python
+from third_party import (
+    lib1, lib2, lib3, lib4,
+    lib5, ...
+)
+```
+
+## 6 - Hanging Grid Grouped
+
+Same as Mode 5. Deprecated.
+
+## 7 - NOQA
+
+```python
+from third_party import lib1, lib2, lib3, ...  # NOQA
+```
+
+Alternatively, you can set `force_single_line` to `True` (`-sl` on the
+command line) and every import will appear on its own line:
+
+```python
+from third_party import lib1
+from third_party import lib2
+from third_party import lib3
+...
+```
+
+## 8 - Vertical Hanging Indent Bracket
+
+Same as Mode 3 - _Vertical Hanging Indent_ but the closing parentheses
+on the last line is indented.
+
+```python
+from third_party import (
+    lib1,
+    lib2,
+    lib3,
+    lib4,
+    )
+```
+
+## 9 - Vertical Prefix From Module Import
+
+Starts a new line with the same `from MODULE import ` prefix when lines are longer than the line length limit.
+
+```python
+from third_party import lib1, lib2, lib3
+from third_party import lib4, lib5, lib6
+```
+
+## 10 - Hanging Indent With Parentheses
+
+Same as Mode 2 - _Hanging Indent_ but uses parentheses instead of backslash
+for wrapping long lines.
+
+```python
+from third_party import (
+    lib1, lib2, lib3,
+    lib4, lib5, lib6)
+```
+
+## 11 - Backslash Grid
+
+Same as Mode 0 - _Grid_ but uses backslashes instead of parentheses to group imports.
+
+```python
+from third_party import lib1, lib2, lib3, \
+                        lib4, lib5
+```