supplier-meesho.webflow 1.0.0

package/GitRepos/isort/README.md

@@ -0,0 +1,355 @@
+[![isort - isort your imports, so you don't have to.](https://raw.githubusercontent.com/pycqa/isort/main/art/logo_large.png)](https://pycqa.github.io/isort/)
+
+------------------------------------------------------------------------
+
+[![PyPI version](https://badge.fury.io/py/isort.svg)](https://badge.fury.io/py/isort)
+[![Test Status](https://github.com/pycqa/isort/workflows/Test/badge.svg?branch=develop)](https://github.com/pycqa/isort/actions?query=workflow%3ATest)
+[![Lint Status](https://github.com/pycqa/isort/workflows/Lint/badge.svg?branch=develop)](https://github.com/pycqa/isort/actions?query=workflow%3ALint)
+[![Code coverage Status](https://codecov.io/gh/pycqa/isort/branch/main/graph/badge.svg)](https://codecov.io/gh/pycqa/isort)
+[![License](https://img.shields.io/github/license/mashape/apistatus.svg)](https://pypi.org/project/isort/)
+[![Join the chat at https://gitter.im/timothycrosley/isort](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/timothycrosley/isort?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+[![Downloads](https://pepy.tech/badge/isort)](https://pepy.tech/project/isort)
+[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
+[![Imports: isort](https://img.shields.io/badge/%20imports-isort-%231674b1?style=flat&labelColor=ef8336)](https://pycqa.github.io/isort/)
+[![DeepSource](https://static.deepsource.io/deepsource-badge-light-mini.svg)](https://deepsource.io/gh/pycqa/isort/?ref=repository-badge)
+_________________
+
+[Read Latest Documentation](https://pycqa.github.io/isort/) - [Browse GitHub Code Repository](https://github.com/pycqa/isort/)
+_________________
+
+isort your imports, so you don't have to.
+
+isort is a Python utility / library to sort imports alphabetically, and
+automatically separated into sections and by type. It provides a command line
+utility, Python library and [plugins for various
+editors](https://github.com/pycqa/isort/wiki/isort-Plugins) to
+quickly sort all your imports. It requires Python 3.6+ to run but
+supports formatting Python 2 code too.
+
+- [Try isort now from your browser!](https://pycqa.github.io/isort/docs/quick_start/0.-try/)
+- [Using black? See the isort and black compatiblity guide.](https://pycqa.github.io/isort/docs/configuration/black_compatibility/)
+- [isort has official support for pre-commit!](https://pycqa.github.io/isort/docs/configuration/pre-commit/)
+
+![Example Usage](https://raw.github.com/pycqa/isort/main/example.gif)
+
+Before isort:
+
+```python
+from my_lib import Object
+
+import os
+
+from my_lib import Object3
+
+from my_lib import Object2
+
+import sys
+
+from third_party import lib15, lib1, lib2, lib3, lib4, lib5, lib6, lib7, lib8, lib9, lib10, lib11, lib12, lib13, lib14
+
+import sys
+
+from __future__ import absolute_import
+
+from third_party import lib3
+
+print("Hey")
+print("yo")
+```
+
+After isort:
+
+```python
+from __future__ import absolute_import
+
+import os
+import sys
+
+from third_party import (lib1, lib2, lib3, lib4, lib5, lib6, lib7, lib8,
+                         lib9, lib10, lib11, lib12, lib13, lib14, lib15)
+
+from my_lib import Object, Object2, Object3
+
+print("Hey")
+print("yo")
+```
+
+## Installing isort
+
+Installing isort is as simple as:
+
+```bash
+pip install isort
+```
+
+Install isort with requirements.txt support:
+
+```bash
+pip install isort[requirements_deprecated_finder]
+```
+
+Install isort with Pipfile support:
+
+```bash
+pip install isort[pipfile_deprecated_finder]
+```
+
+Install isort with both formats support:
+
+```bash
+pip install isort[requirements_deprecated_finder,pipfile_deprecated_finder]
+```
+
+## Using isort
+
+**From the command line**:
+
+To run on specific files:
+
+```bash
+isort mypythonfile.py mypythonfile2.py
+```
+
+To apply recursively:
+
+```bash
+isort .
+```
+
+If [globstar](https://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html)
+is enabled, `isort .` is equivalent to:
+
+```bash
+isort **/*.py
+```
+
+To view proposed changes without applying them:
+
+```bash
+isort mypythonfile.py --diff
+```
+
+Finally, to atomically run isort against a project, only applying
+changes if they don't introduce syntax errors:
+
+```bash
+isort --atomic .
+```
+
+(Note: this is disabled by default, as it prevents isort from
+running against code written using a different version of Python.)
+
+**From within Python**:
+
+```python
+import isort
+
+isort.file("pythonfile.py")
+```
+
+or:
+
+```python
+import isort
+
+sorted_code = isort.code("import b\nimport a\n")
+```
+
+## Installing isort's for your preferred text editor
+
+Several plugins have been written that enable to use isort from within a
+variety of text-editors. You can find a full list of them [on the isort
+wiki](https://github.com/pycqa/isort/wiki/isort-Plugins).
+Additionally, I will enthusiastically accept pull requests that include
+plugins for other text editors and add documentation for them as I am
+notified.
+
+## Multi line output modes
+
+You will notice above the \"multi\_line\_output\" setting. This setting
+defines how from imports wrap when they extend past the line\_length
+limit and has [12 possible settings](https://pycqa.github.io/isort/docs/configuration/multi_line_output_modes/).
+
+## Indentation
+
+To change the how constant indents appear - simply change the
+indent property with the following accepted formats:
+
+-   Number of spaces you would like. For example: 4 would cause standard
+    4 space indentation.
+-   Tab
+-   A verbatim string with quotes around it.
+
+For example:
+
+```python
+"    "
+```
+
+is equivalent to 4.
+
+For the import styles that use parentheses, you can control whether or
+not to include a trailing comma after the last import with the
+`include_trailing_comma` option (defaults to `False`).
+
+## Intelligently Balanced Multi-line Imports
+
+As of isort 3.1.0 support for balanced multi-line imports has been
+added. With this enabled isort will dynamically change the import length
+to the one that produces the most balanced grid, while staying below the
+maximum import length defined.
+
+Example:
+
+```python
+from __future__ import (absolute_import, division,
+                        print_function, unicode_literals)
+```
+
+Will be produced instead of:
+
+```python
+from __future__ import (absolute_import, division, print_function,
+                        unicode_literals)
+```
+
+To enable this set `balanced_wrapping` to `True` in your config or pass
+the `-e` option into the command line utility.
+
+## Custom Sections and Ordering
+
+isort provides configuration options to change almost every aspect of how
+imports are organized, ordered, or grouped together in sections.
+
+[Click here](https://pycqa.github.io/isort/docs/configuration/custom_sections_and_ordering/) for an overview of all these options.
+
+## Skip processing of imports (outside of configuration)
+
+To make isort ignore a single import simply add a comment at the end of
+the import line containing the text `isort:skip`:
+
+```python
+import module  # isort:skip
+```
+
+or:
+
+```python
+from xyz import (abc,  # isort:skip
+                 yo,
+                 hey)
+```
+
+To make isort skip an entire file simply add `isort:skip_file` to the
+module's doc string:
+
+```python
+""" my_module.py
+    Best module ever
+
+   isort:skip_file
+"""
+
+import b
+import a
+```
+
+## Adding or removing an import from multiple files
+
+isort can be ran or configured to add / remove imports automatically.
+
+[See a complete guide here.](https://pycqa.github.io/isort/docs/configuration/add_or_remove_imports/)
+
+## Using isort to verify code
+
+The `--check-only` option
+-------------------------
+
+isort can also be used to verify that code is correctly formatted
+by running it with `-c`. Any files that contain incorrectly sorted
+and/or formatted imports will be outputted to `stderr`.
+
+```bash
+isort **/*.py -c -v
+
+SUCCESS: /home/timothy/Projects/Open_Source/isort/isort_kate_plugin.py Everything Looks Good!
+ERROR: /home/timothy/Projects/Open_Source/isort/isort/isort.py Imports are incorrectly sorted.
+```
+
+One great place this can be used is with a pre-commit git hook, such as
+this one by \@acdha:
+
+<https://gist.github.com/acdha/8717683>
+
+This can help to ensure a certain level of code quality throughout a
+project.
+
+## Git hook
+
+isort provides a hook function that can be integrated into your Git
+pre-commit script to check Python code before committing.
+
+[More info here.](https://pycqa.github.io/isort/docs/configuration/git_hook/)
+
+## Setuptools integration
+
+Upon installation, isort enables a `setuptools` command that checks
+Python files declared by your project.
+
+[More info here.](https://pycqa.github.io/isort/docs/configuration/setuptools_integration/)
+
+## Spread the word
+
+[![Imports: isort](https://img.shields.io/badge/%20imports-isort-%231674b1?style=flat&labelColor=ef8336)](https://pycqa.github.io/isort/)
+
+Place this badge at the top of your repository to let others know your project uses isort.
+
+For README.md:
+
+```markdown
+[![Imports: isort](https://img.shields.io/badge/%20imports-isort-%231674b1?style=flat&labelColor=ef8336)](https://pycqa.github.io/isort/)
+```
+
+Or README.rst:
+
+```rst
+.. image:: https://img.shields.io/badge/%20imports-isort-%231674b1?style=flat&labelColor=ef8336
+    :target: https://pycqa.github.io/isort/
+```
+
+## Security contact information
+
+To report a security vulnerability, please use the [Tidelift security
+contact](https://tidelift.com/security). Tidelift will coordinate the
+fix and disclosure.
+
+## Why isort?
+
+isort simply stands for import sort. It was originally called
+"sortImports" however I got tired of typing the extra characters and
+came to the realization camelCase is not pythonic.
+
+I wrote isort because in an organization I used to work in the manager
+came in one day and decided all code must have alphabetically sorted
+imports. The code base was huge - and he meant for us to do it by hand.
+However, being a programmer - I\'m too lazy to spend 8 hours mindlessly
+performing a function, but not too lazy to spend 16 hours automating it.
+I was given permission to open source sortImports and here we are :)
+
+------------------------------------------------------------------------
+
+[Get professionally supported isort with the Tidelift
+Subscription](https://tidelift.com/subscription/pkg/pypi-isort?utm_source=pypi-isort&utm_medium=referral&utm_campaign=readme)
+
+Professional support for isort is available as part of the [Tidelift
+Subscription](https://tidelift.com/subscription/pkg/pypi-isort?utm_source=pypi-isort&utm_medium=referral&utm_campaign=readme).
+Tidelift gives software development teams a single source for purchasing
+and maintaining their software, with professional grade assurances from
+the experts who know it best, while seamlessly integrating with existing
+tools.
+
+------------------------------------------------------------------------
+
+Thanks and I hope you find isort useful!
+
+~Timothy Crosley

package/GitRepos/isort/art/stylesheets/extra.css

@@ -0,0 +1,5 @@
+[data-md-color-scheme="isort"] {
+  --md-primary-fg-color:        #EF8336;
+  --md-primary-fg-color--light: #1674B1;
+  --md-primary-fg-color--dark:  #1674b1;
+}

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

@@ -0,0 +1,108 @@
+# Action Comments
+
+The most basic way to configure the flow of isort within a single file is action comments. These comments are picked up and interpreted by the isort parser during parsing.
+
+
+## isort: skip_file
+
+Tells isort to skip the entire file.
+
+Example:
+
+```python
+# !/bin/python3
+# isort: skip_file
+import os
+import sys
+
+...
+```
+
+!!! warning
+    This should be placed as high in the file as reasonably possible.
+    Since isort uses a streaming architecture, it may have already completed some work before it reaches the comment. Usually, this is okay - but can be confusing if --diff or any interactive options are used from the command line.
+
+
+## isort: skip
+
+If placed on the same line as (or within the continuation of a) an import statement, isort will not sort this import.
+More specifically, it prevents the import statement from being recognized by isort as an import. In consequence, this line will be treated as code and be pushed down to below the import section of the file.
+
+Example:
+
+```python
+import b
+import a # isort: skip <- this will now stay below b
+```
+!!! note
+    It is recommended to where possible use `# isort: off` and `# isort: on` or `# isort: split` instead as the behavior is more explicit and predictable.
+
+## isort: off
+
+Turns isort parsing off. Every line after an `# isort: off` statement will be passed along unchanged until an `# isort: on` comment or the end of the file.
+
+Example:
+
+```python
+import e
+import f
+
+# isort: off
+
+import b
+import a
+```
+
+## isort: on
+
+Turns isort parsing back on. This only makes sense if an `# isort: off` comment exists higher in the file! This allows you to have blocks of unsorted imports, around otherwise sorted ones.
+
+Example:
+
+```python
+
+import e
+import f
+
+# isort: off
+
+import b
+import a
+
+# isort: on
+
+import c
+import d
+
+```
+
+## isort: split
+
+Tells isort the current sort section is finished, and all future imports belong to a new sort grouping.
+
+Example:
+
+```python
+
+import e
+import f
+
+# isort: split
+
+import a
+import b
+import c
+import d
+
+```
+
+You can also use it inline to keep an import from having imports above or below it swap position:
+
+```python
+import c
+import b  # isort: split
+import a
+```
+
+!!! tip
+    isort split is exactly the same as placing an `# isort: on` immediately below an `# isort: off`

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

@@ -0,0 +1,28 @@
+
+## Adding an import to multiple files
+isort makes it easy to add an import statement across multiple files,
+while being assured it's correctly placed.
+
+To add an import to all files:
+
+```bash
+isort -a "from __future__ import print_function" *.py
+```
+
+To add an import only to files that already have imports:
+
+```bash
+isort -a "from __future__ import print_function" --append-only *.py
+```
+
+
+## Removing an import from multiple files
+
+isort also makes it easy to remove an import from multiple files,
+without having to be concerned with how it was originally formatted.
+
+From the command line:
+
+```bash
+isort --rm "os.system" *.py
+```

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

@@ -0,0 +1,63 @@
+![isort loves black](https://raw.githubusercontent.com/pycqa/isort/main/art/isort_loves_black.png)
+
+Compatibility with black
+========
+
+Compatibility with black is very important to the isort project and comes baked in starting with version 5.
+All that's required to use isort alongside black is to set the isort profile to "black".
+
+## Using a config file (such as .isort.cfg)
+
+For projects that officially use both isort and black, we recommend setting the black profile in a config file at the root of your project's repository.
+This way independent to how users call isort (pre-commit, CLI, or editor integration) the black profile will automatically be applied.
+
+For instance, your _pyproject.toml_ file would look something like
+
+```ini
+[tool.isort]
+profile = "black"
+multi_line_output = 3
+```
+
+Read More about supported [config files](https://pycqa.github.io/isort/docs/configuration/config_files/).
+
+## CLI
+
+To use the profile option when calling isort directly from the commandline simply add the --profile black argument: `isort --profile black`.
+
+A demo of how this would look like in your _.travis.yml_
+
+```yaml
+language: python
+python:
+  - "3.6"
+  - "3.7"
+  - "3.8"
+
+install:
+  - pip install -r requirements-dev.txt
+  - pip install isort black
+  - pip install coveralls
+script:
+  - pytest my-package
+  - isort --profile black my-package
+  - black --check --diff my-package
+after_success:
+  - coveralls
+
+```
+
+See [built-in profiles](https://pycqa.github.io/isort/docs/configuration/profiles/) for more profiles.
+
+## Integration with pre-commit
+
+You can also set the profile directly when integrating isort within pre-commit.
+
+```yaml
+- repo: https://github.com/pycqa/isort
+    rev: 5.6.4
+    hooks:
+      - id: isort
+        args: ["--profile", "black", "--filter-files"]
+```
+

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

@@ -0,0 +1,89 @@
+Supported Config Files
+========
+
+isort supports various standard config formats to allow customizations to be integrated into any project quickly.
+When applying configurations, isort looks for the closest supported config file, in the order files are listed below.
+You can manually specify the settings file or path by setting `--settings-path` from the command-line. Otherwise, isort will
+traverse up to 25 parent directories until it finds a suitable config file.
+Note that isort will not leave a git or Mercurial repository (checking for a `.git` or `.hg` directory).
+As soon as it finds a file, it stops looking. The config file search is done relative to the current directory if `isort .`
+or a file stream is passed in, or relative to the first path passed in if multiple paths are passed in.
+isort **never** merges config files together due to the confusion it can cause.
+
+!!! tip
+    You can always introspect the configuration settings isort determined, and find out which config file it picked up, by running `isort . --show-config`
+
+
+
+## .isort.cfg **[preferred format]**
+
+The first place isort will look for settings is in dedicated .isort.cfg files.
+The advantage of using this kind of config file, is that it is explicitly for isort and follows a well understood format.
+The downside, is that it means one more config file in your project when you may already have several polluting your file hierarchy.
+
+An example a config from the isort project itself:
+
+```ini
+[settings]
+profile=hug
+src_paths=isort,test
+```
+
+## pyproject.toml **[preferred format]**
+
+The second place isort will look, and an equally excellent choice to place your configuration, is within a pyproject.toml file.
+The advantage of using this config file, is that it is quickly becoming a standard place to configure all Python tools.
+This means other developers will know to look here and you will keep your projects root nice and tidy.
+The only disadvantage is that other tools you use might not yet support this format, negating the cleanliness.
+
+```toml
+[tool.isort]
+profile = "hug"
+src_paths = ["isort", "test"]
+```
+
+## setup.cfg
+
+`setup.cfg` can be thought of as the precursor to `pyproject.toml`. While isort and newer tools are increasingly moving to pyproject.toml, if you rely on many tools that
+use this standard it can be a natural fit to put your isort config there as well.
+
+
+```ini
+[isort]
+profile=hug
+src_paths=isort,test
+```
+
+## tox.ini
+
+[tox](https://tox.readthedocs.io/en/latest/) is a tool commonly used in the Python community to specify multiple testing environments.
+Because isort verification is commonly ran as a testing step, some prefer to place the isort config inside of the tox.ini file.
+
+```ini
+[isort]
+```
+
+## .editorconfig
+
+Finally, isort will look for a `.editorconfig` configuration with settings for Python source files. [EditorConfig](https://editorconfig.org/) is a project to enable specifying a configuration for text editing behaviour once, allowing multiple command line tools and text editors to pick it up. Since isort cares about a lot of the same settings as a text-editor (like line-length) it makes sense for it to look within these files
+as well.
+
+```
+root = true
+
+[*.py]
+profile = hug
+indent_style = space
+indent_size = 4
+skip = build,.tox,venv
+src_paths=isort,test
+```
+
+## Custom config files
+
+Optionally, you can also create a config file with a custom name, or directly point isort to a config file that falls lower in the priority order, by using [--settings-file](https://pycqa.github.io/isort/docs/configuration/options/#settings-path).
+This can be useful, for instance, if you want to have one configuration for `.py` files and another for `.pyx` - while keeping the config files at the root of your repository.
+
+!!! tip
+    Custom config files should place their configuration options inside an `[isort]` section and never a generic `[settings]` section. This is because isort can't know for sure
+    how other tools are utilizing the config file.