supplier-meesho.webflow 1.0.0

package/GitRepos/isort/docs/configuration/pre-commit.md

@@ -0,0 +1,32 @@
+Using isort with pre-commit
+========
+
+isort provides official support for [pre-commit](https://pre-commit.com/).
+
+### isort pre-commit step
+
+To use isort's official pre-commit integration add the following config:
+
+```
+  - repo: https://github.com/pycqa/isort
+    rev: 5.8.0
+    hooks:
+      - id: isort
+        name: isort (python)
+      - id: isort
+        name: isort (cython)
+        types: [cython]
+      - id: isort
+        name: isort (pyi)
+        types: [pyi]
+```
+
+under the `repos` section of your projects `.pre-commit-config.yaml` file.
+
+### seed-isort-config
+
+Older versions of isort used a lot of magic to determine import placement, that could easily break when running on CI/CD.
+To fix this, a utilitiy called `seed-isort-config` was created. Since isort 5 however, the project has drastically improved its placement
+logic and ensured a good level of consistency across environments.
+If you have a step in your pre-commit config called `seed-isort-config` or similar, it is highly recommend that you remove this.
+It is guaranteed to slow things down, and can conflict with isort's own module placement logic.

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

@@ -0,0 +1,86 @@
+Built-in Profile for isort
+========
+
+The following profiles are built into isort to allow easy interoperability with
+common projects and code styles.
+
+To use any of the listed profiles, use `isort --profile PROFILE_NAME` from the command line, or `profile=PROFILE_NAME` in your configuration file.
+
+
+#black
+
+
+ - **multi_line_output**: `3`
+ - **include_trailing_comma**: `True`
+ - **force_grid_wrap**: `0`
+ - **use_parentheses**: `True`
+ - **ensure_newline_before_comments**: `True`
+ - **line_length**: `88`
+
+#django
+
+
+ - **combine_as_imports**: `True`
+ - **include_trailing_comma**: `True`
+ - **multi_line_output**: `5`
+ - **line_length**: `79`
+
+#pycharm
+
+
+ - **multi_line_output**: `3`
+ - **force_grid_wrap**: `2`
+ - **lines_after_imports**: `2`
+
+#google
+
+
+ - **force_single_line**: `True`
+ - **force_sort_within_sections**: `True`
+ - **lexicographical**: `True`
+ - **single_line_exclusions**: `('typing',)`
+ - **order_by_type**: `False`
+ - **group_by_package**: `True`
+
+#open_stack
+
+
+ - **force_single_line**: `True`
+ - **force_sort_within_sections**: `True`
+ - **lexicographical**: `True`
+
+#plone
+
+
+ - **force_alphabetical_sort**: `True`
+ - **force_single_line**: `True`
+ - **lines_after_imports**: `2`
+ - **line_length**: `200`
+
+#attrs
+
+
+ - **atomic**: `True`
+ - **force_grid_wrap**: `0`
+ - **include_trailing_comma**: `True`
+ - **lines_after_imports**: `2`
+ - **lines_between_types**: `1`
+ - **multi_line_output**: `3`
+ - **use_parentheses**: `True`
+
+#hug
+
+
+ - **multi_line_output**: `3`
+ - **include_trailing_comma**: `True`
+ - **force_grid_wrap**: `0`
+ - **use_parentheses**: `True`
+ - **line_length**: `100`
+
+#wemake
+
+
+ - **multi_line_output**: `3`
+ - **include_trailing_comma**: `True`
+ - **use_parentheses**: `True`
+ - **line_length**: `80`

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

@@ -0,0 +1,27 @@
+# Setuptools integration
+
+Upon installation, isort enables a `setuptools` command that checks
+Python files declared by your project.
+
+Running `python setup.py isort` on the command line will check the files
+listed in your `py_modules` and `packages`. If any warning is found, the
+command will exit with an error code:
+
+```bash
+$ python setup.py isort
+```
+
+Also, to allow users to be able to use the command without having to
+install isort themselves, add isort to the setup\_requires of your
+`setup()` like so:
+
+```python
+setup(
+    name="project",
+    packages=["project"],
+
+    setup_requires=[
+        "isort"
+    ]
+)
+```

package/GitRepos/isort/docs/contributing/1.-contributing-guide.md

@@ -0,0 +1,81 @@
+Contributing to isort
+========
+
+Looking for a useful open source project to contribute to?
+Want your contributions to be warmly welcomed and acknowledged?
+Welcome! You have found the right place.
+
+## Getting isort set up for local development
+The first step when contributing to any project is getting it set up on your local machine. isort aims to make this as simple as possible.
+
+Account Requirements:
+
+- [A valid GitHub account](https://github.com/join)
+
+Base System Requirements:
+
+- Python3.6+
+- poetry
+- bash or a bash compatible shell (should be auto-installed on Linux / Mac)
+  - WSL users running Ubuntu may need to install Python's venv module even after installing Python.
+
+Once you have verified that your system matches the base requirements you can start to get the project working by following these steps:
+
+1. [Fork the project on GitHub](https://github.com/pycqa/isort/fork).
+2. Clone your fork to your local file system:
+    `git clone https://github.com/$GITHUB_ACCOUNT/isort.git`
+3. `cd isort`
+4. `poetry install`
+   * Optionally, isolate poetry's installation from the rest of your system using the instructions on the poetry site here:  https://python-poetry.org/docs/#installation
+5. `./scripts/test.sh` should yield Success: no issues found
+6. `./scripts/clean.sh` should yield a Safety report checking packages
+
+**TIP**: `./scripts/done.sh` will run both clean and test in one step.
+
+### Docker development
+
+If you would instead like to develop using Docker, the only local requirement is docker.
+See the [docker docs](https://docs.docker.com/get-started/) if you have not used docker before.
+
+Once you have the docker daemon running and have cloned the repository, you can get started by following these steps:
+
+1. `cd isort`
+2. `./scripts/docker.sh`
+
+A local test cycle might look like the following:
+
+1. `docker build ./ -t isort:latest`
+2. `docker run isort`
+3. if #2 fails, debug, save, and goto #1
+    * `docker run -it isort bash` will get you into the failed environment
+    * `docker run -v $(git rev-parse --show-toplevel):/isort` will make changes made in the docker environment persist on your local checkout.
+      **TIP**: combine both to get an interacive docker shell that loads changes made locally, even after build, to quickly rerun that pesky failing test
+4. `./scripts/docker.sh`
+5. if #4 fails, debug, save and goto #1; you may need to specify a different `--build-arg VERSION=$VER`
+6. congrats! you are probably ready to push a contribution
+
+## Making a contribution
+Congrats! You're now ready to make a contribution! Use the following as a guide to help you reach a successful pull-request:
+
+1. Check the [issues page](https://github.com/pycqa/isort/issues) on GitHub to see if the task you want to complete is listed there.
+    - If it's listed there, write a comment letting others know you are working on it.
+    - If it's not listed in GitHub issues, go ahead and log a new issue. Then add a comment letting everyone know you have it under control.
+        - If you're not sure if it's something that is good for the main isort project and want immediate feedback, you can discuss it [here](https://gitter.im/timothycrosley/isort).
+2. Create an issue branch for your local work `git checkout -b issue/$ISSUE-NUMBER`.
+3. Do your magic here.
+4. Ensure your code matches the [HOPE-8 Coding Standard](https://github.com/hugapi/HOPE/blob/master/all/HOPE-8--Style-Guide-for-Hug-Code.md#hope-8----style-guide-for-hug-code) used by the project.
+5. Run tests locally to make sure everything is still working
+	`./scripts/done.sh`
+	_Or if you are using Docker_
+	`docker run isort:latest`
+6. Submit a pull request to the main project repository via GitHub.
+
+Thanks for the contribution! It will quickly get reviewed, and, once accepted, will result in your name being added to the acknowledgments list :).
+
+## Thank you!
+I can not tell you how thankful I am for the hard work done by isort contributors like *you*.
+
+Thank you!
+
+~Timothy Crosley
+

package/GitRepos/isort/docs/contributing/2.-coding-standard.md

@@ -0,0 +1,57 @@
+# HOPE 8 -- Style Guide for Hug Code
+
+|             |                                             |
+| ------------| ------------------------------------------- |
+| HOPE:       | 8                                           |
+| Title:      | Style Guide for Hug Code                    |
+| Author(s):  | Timothy Crosley <timothy.crosley@gmail.com> |
+| Status:     | Active                                      |
+| Type:       | Process                                     |
+| Created:    | 19-May-2019                                 |
+| Updated:    | 17-August-2019                                 |
+
+## Introduction
+
+This document gives coding conventions for the Hug code comprising the Hug core as well as all official interfaces, extensions, and plugins for the framework.
+Optionally, projects that use Hug are encouraged to follow this HOPE and link to it as a reference.
+
+## PEP 8 Foundation
+
+All guidelines in this document are in addition to those defined in Python's [PEP 8](https://www.python.org/dev/peps/pep-0008/) and [PEP 257](https://www.python.org/dev/peps/pep-0257/) guidelines.
+
+## Line Length
+
+Too short of lines discourage descriptive variable names where they otherwise make sense.
+Too long of lines reduce overall readability and make it hard to compare 2 files side by side.
+There is no perfect number: but for Hug, we've decided to cap the lines at 100 characters.
+
+## Descriptive Variable names
+
+Naming things is hard. Hug has a few strict guidelines on the usage of variable names, which hopefully will reduce some of the guesswork:
+- No one character variable names.
+    - Except for x, y, and z as coordinates.
+- It's not okay to override built-in functions.
+    - Except for `id`. Guido himself thought that shouldn't have been moved to the system module. It's too commonly used, and alternatives feel very artificial.
+- Avoid Acronyms, Abbreviations, or any other short forms - unless they are almost universally understand.
+
+## Adding new modules
+
+New modules added to the a project that follows the HOPE-8 standard should all live directly within the base `PROJECT_NAME/` directory without nesting. If the modules are meant only for internal use within the project, they should be prefixed with a leading underscore. For example, def _internal_function. Modules should contain a docstring at the top that gives a general explanation of the purpose and then restates the project's use of the MIT license.
+There should be a `tests/test_$MODULE_NAME.py` file created to correspond to every new module that contains test coverage for the module. Ideally, tests should be 1:1 (one test object per code object, one test method per code method) to the extent cleanly possible.
+
+## Automated Code Cleaners
+
+All code submitted to Hug should be formatted using Black and isort.
+Black should be run with the line length set to 100, and isort with Black compatible settings in place.
+
+## Automated Code Linting
+
+All code submitted to hug should run through the following tools:
+
+- Black and isort verification.
+- Flake8
+   - flake8-bugbear
+- Bandit
+- pep8-naming
+- vulture
+- safety

package/GitRepos/isort/docs/contributing/3.-code-of-conduct.md

@@ -0,0 +1,88 @@
+# HOPE 11 -- Code of Conduct
+
+|             |                                             |
+| ------------| ------------------------------------------- |
+| HOPE:       | 11                                          |
+| Title:      | Code of Conduct                             |
+| Author(s):  | Timothy Crosley <timothy.crosley@gmail.com> |
+| Status:     | Active                                      |
+| Type:       | Process                                     |
+| Created:    | 17-August-2019                              |
+| Updated:    | 17-August-2019                              |
+
+## Abstract
+
+Defines the Code of Conduct for Hug and all related projects.
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting [timothy.crosley@gmail.com](mailto:timothy.crosley@gmail.com). All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. Confidentiality will be maintained
+with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][https://www.contributor-covenant.org], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

package/GitRepos/isort/docs/contributing/4.-acknowledgements.md

@@ -0,0 +1,259 @@
+Core Developers
+===================
+- Aniruddha Bhattacharjee (@anirudnits)
+- Jon Dufresne (@jdufresne)
+- Tamas Szabo (@sztamas)
+- Timothy Edmund Crosley (@timothycrosley)
+
+Plugin Writers
+===================
+- *VIM* - Juan Pedro Fisanotti (@fisadev)
+- *Emacs* - Friedrich Paetzke (@paetzke)
+- *Sublime* - Thijs de Zoute (@thijsdezoete)
+
+Notable Bug Reporters
+===================
+- Bengt Lüers (@Bengt)
+- Chris Adams (@acdha)
+- @OddBloke
+- Martin Geisler (@mgeisler)
+- Tim Heap (@timheap)
+- Matěj Nikl (@MatejNikl)
+
+Code Contributors
+===================
+- Aaron Gallagher (@habnabit)
+- Thomas Grainger (@graingert)
+- Thijs de Zoute (@thijsdezoete)
+- Marc Abramowitz (@msabramo)
+- Daniel Cowgill (@dcowgill)
+- Francois Lebel (@flebel)
+- Antoni Segura Puimedon (@celebdor)
+- Pablo (@oubiga)
+- Oskar Hahn (@ostcar)
+- Wim Glenn (@wimglenn)
+- Matt Caldwell (@mattcaldwell)
+- Dwayne Bailey (@dwaynebailey)
+- Ionel Cristian Mărieș (@ionelmc)
+- Chris Adams (@acdha)
+- GuoJing (@GuoJing)
+- George Hickman (@ghickman)
+- Dan Davison (@dandavison)
+- Maciej Wolff (@maciejwo)
+- Elliott Sales de Andrade (@qulogic)
+- Kasper Jacobsen (@dinoshauer)
+- Sebastian Pipping (@hartwork)
+- Helen Sherwood-Taylor (@helenst)
+- Mocker (@Zuckonit)
+- Tim Graham (@timgraham)
+- Adam (@NorthIsUp)
+- Norman Jäckel (@normanjaeckel)
+- Derrick Petzold (@dpetzold)
+- Michael van Tellingen (@mvantellingen)
+- Patrick Yevsukov (@patrickyevsukov)
+- Christer van der Meeren (@cmeeren)
+- Timon Wong/NHNCN (@timonwong)
+- Jeremy Dunck (@jdunck)
+- Benjamin ABEL (@benjaminabel)
+- Dan Baragan (@danbaragan)
+- Rob Cowie (@robcowie)
+- Amit Shah (@Amwam)
+- Patrick Gerken (@do3cc)
+- @dein0s
+- David Stensland (@terite)
+- Ankur Dedania (@AbsoluteMSTR)
+- Lee Packham (@leepa)
+- Jesse Mullan (@jmullan)
+- Kwok-kuen Cheung (@cheungpat)
+- Johan Bloemberg (@aequitas)
+- Dan Watson (@dcwatson)
+- Éric Araujo (@merwok)
+- Dan Palmer (@danpalmer)
+- Andy Boot (@bootandy)
+- @m7v8
+- John Vandenberg (@jayvdb)
+- Adam Chainz (@adamchainz)
+- @Brightcells
+- Jonas Trappenberg (@teeberg)
+- Andrew Konstantaras (@akonsta)
+- Jason Brackman (@jasonbrackman)
+- Kathryn Lingel (@katlings)
+- Andrew Gaul (@gaul)
+- John Chadwick (@jchv)
+- Jon Dufresne (@jdufresne)
+- Brian F. Baron (@briabar)
+- Madison Caldwell (@madirey)
+- Matt Yule-Bennett (@mattbennett)
+- Jaswanth Kumar (@jaswanth098)
+- Dario Navin (@Zarathustra2)
+- Danny Weinberg (@FuegoFro)
+- Gram (@orsinium)
+- Hugo van Kemenade (@hugovk)
+- Géry Ogam (@maggyero)
+- Cody Scott (@Siecje)
+- Pedro Algarvio (@s0undt3ch)
+- Chris St. Pierre (@stpierre)
+- Sebastian Rittau (@srittau)
+- João M.C. Teixeira (@joaomcteixeira)
+- Honnix (@honnix)
+- Anders Kaseorg (@andersk)
+- @r-richmond
+- Sebastian (@sebix)
+- Kosei Kitahara (@Surgo)
+- Seung Hyeon, Kim (@hyeonjames)
+- Gerard Dalmau (@gdalmau)
+- Robert Tasarz (@rtasarz)
+- Ryo Miyajima (@sergeant-wizard)
+- @mdagaro
+- Maksim Kurnikov (@mkurnikov)
+- Daniel Hahler (@blueyed)
+- @ucodery
+- Aarni Koskela (@akx)
+- Alex Chan (@alexwlchan)
+- Rick Thomas (@richardlthomas)
+- Jeppe Fihl-Pearson (@Tenzer)
+- Jonas Lundberg (@lundberg)
+- Neil (@NeilGirdhar)
+- @dmanikowski-reef
+- Stephen Brown II (@StephenBrown2)
+- Ankur Dedania (@AnkurDedania)
+- Anthony Sottile (@asottile)
+- Bendik Samseth (@bsamseth)
+- Dan W Anderson (@anderson-dan-w)
+- DeepSource Bot (@deepsourcebot)
+- Mitar (@mitar)
+- Omer Katz (@thedrow)
+- Santiago Castro (@bryant1410)
+- Sergey Fursov (@GeyseR)
+- Thomas Robitaille (@astrofrog)
+- Ville Skyttä (@scop)
+- Hakan Çelik (@hakancelik96)
+- Dylan Katz (@Plazmaz)
+- Linus Lewandowski (@LEW21)
+- Bastien Gérard (@bagerard)
+- Brian Dombrowski (@bdombro)
+- Ed Morley (@edmorley)
+- Graeme Coupar (@obmarg)
+- Jerome Leclanche (@jleclanche)
+- Joshu Coats (@rhwlo)
+- Mansour Behabadi (@oxplot)
+- Sam Lai (@slai)
+- Tamas Szabo (@sztamas)
+- Yedidyah Bar David (@didib)
+- Hidetoshi Hirokawa (@h-hirokawa)
+- Aaron Chong (@acjh)
+- Harai Akihiro (@harai)
+- Andy Freeland (@rouge8)
+- @ethifus
+- Joachim Brandon LeBlanc (@demosdemon)
+- Brian May (@brianmay)
+- Bruno Oliveira (@nicoddemus)
+- Bruno Renié (@brutasse)
+- Bryce Guinta (@brycepg)
+- David Chan (@dchanm)
+- David Smith (@smithdc1)
+- Irv Lustig (@Dr-Irv)
+- Dylan Richardson (@dylrich)
+- Emil Melnikov (@emilmelnikov)
+- Eric Johnson (@metrizable)
+- @ryabtsev
+- Felix Yan (@felixonmars)
+- Gil Forcada Codinachs (@gforcada)
+- Ilya Konstantinov (@ikonst)
+- Jace Browning (@jacebrowning)
+- Jin Suk Park (@jinmel)
+- Jürgen Gmach (@jugmac00)
+- Maciej Gawinecki (@dzieciou)
+- Minn Soe (@MinnSoe)
+- Nikolaus Wittenstein (@adzenith)
+- Norman J. Harman Jr. (@njharman)
+- P R Gurunath (@gurunath-p)
+- Patrick Hayes (@pfhayes)
+- Pete Grayson (@jpgrayson)
+- Philip Jenvey (@pjenvey)
+- Rajiv Bakulesh Shah (@brainix)
+- Reid D McKenzie (@arrdem)
+- Robert DeRose (@RobertDeRose)
+- Roey Darwish Dror (@r-darwish)
+- Rudinei Goi Roecker (@rudineirk)
+- Wagner (@wagner-certat)
+- Nikita Sobolev (@sobolevn)
+- Terence Honles (@terencehonles)
+- The Gitter Badger (@gitter-badger)
+- Tim Gates (@timgates42)
+- Tim Staley (@timstaley)
+- Vincent Hatakeyama (@vincent-hatakeyama)
+- Yaron de Leeuw (@jarondl)
+- @jwg4
+- @nicolelodeon
+- Łukasz Langa (@ambv)
+- Grzegorz Pstrucha (@Gricha)
+- Zac Hatfield-Dodds (@Zac-HD)
+- Jiří Škorpil (@JiriSko)
+- James Winegar (@jameswinegar)
+- Abdullah Dursun (@adursun)
+- Guillaume Lostis (@glostis)
+- Krzysztof Jagiełło (@kjagiello)
+- Nicholas Devenish (@ndevenish)
+- Aniruddha Bhattacharjee (@anirudnits)
+- Alexandre Yang (@AlexandreYang)
+- Andrew Howe (@howeaj)
+- Sang-Heon Jeon (@lntuition)
+- Denis Veselov (@saippuakauppias)
+- James Curtin (@jamescurtin)
+- Marco Gorelli (@MarcoGorelli)
+- Louis Sautier (@sbraz)
+- Timur Kushukov (@timqsh)
+- Bhupesh Varshney (@Bhupesh-V)
+- Rohan Khanna (@rohankhanna)
+- Vasilis Gerakaris (@vgerak)
+- @tonci-bw
+- @jaydesl
+- Tamara (@infinityxxx)
+- Akihiro Nitta (@akihironitta)
+- Samuel Gaist (@sgaist)
+- @dwanderson-intel
+- Quentin Santos (@qsantos)
+- @gofr
+- Pavel Savchenko (@asfaltboy)
+- @dongfangtianyu
+- Christian Clauss (@cclauss)
+- Jon Banafato (@jonafato)
+- ruro (@RuRo)
+- Léni (@legau)
+- keno (Ken Okada) (@kenoss)
+
+Documenters
+===================
+- Reinout van Rees (@reinout)
+- Helen Sherwood-Taylor (@helenst)
+- Elliott Sales de Andrade (@QuLogic)
+- Brian Peiris (@brianpeiris)
+- Tim Graham (@timgraham)
+- Josh Soref (@jsoref)
+- Teg Khanna (@tegkhanna)
+- Sarah Beth Tracy (@sbtries)
+- Aaron Brown (@aaronvbrown)
+- Harutaka Kawamura (@harupy)
+- Brad Solomon (@bsolomon1124)
+- Martynas Mickevičius (@2m)
+- Taneli Hukkinen (@hukkinj1)
+- @r-richmond
+- John Villalovos (@JohnVillalovos)
+- Kosei Kitahara (@Surgo)
+- Marat Sharafutdinov (@decaz)
+- Abtin (@abtinmo)
+- @scottwedge
+- Hasan Ramezani (@hramezani)
+- @hirosassa
+- David Poznik (@dpoznik)
+- Mike Frysinger (@vapier)
+- @DanielFEvans
+
+--------------------------------------------
+
+A sincere thanks to everyone who has helped isort be the great utility it is today!
+It would not be one-hundredth as useful and consistent as it is now without the help of your bug reports,
+commits, and suggestions. You guys rock!
+
+~Timothy Crosley