All patches and comments are welcome. Please squash your changes to logical
commits before using git-format-patch and git-send-email to
patches@git.madduck.net.
If you'd read over the Git project's submission guidelines and adhered to them,
I'd be especially grateful.
1 ![Black Logo](https://raw.githubusercontent.com/psf/black/master/docs/_static/logo2-readme.png)
3 <h2 align="center">The Uncompromising Code Formatter</h2>
6 <a href="https://travis-ci.com/psf/black"><img alt="Build Status" src="https://travis-ci.com/psf/black.svg?branch=master"></a>
7 <a href="https://github.com/psf/black/actions"><img alt="Actions Status" src="https://github.com/psf/black/workflows/Test/badge.svg"></a>
8 <a href="https://github.com/psf/black/actions"><img alt="Actions Status" src="https://github.com/psf/black/workflows/Primer/badge.svg"></a>
9 <a href="https://black.readthedocs.io/en/stable/?badge=stable"><img alt="Documentation Status" src="https://readthedocs.org/projects/black/badge/?version=stable"></a>
10 <a href="https://coveralls.io/github/psf/black?branch=master"><img alt="Coverage Status" src="https://coveralls.io/repos/github/psf/black/badge.svg?branch=master"></a>
11 <a href="https://github.com/psf/black/blob/master/LICENSE"><img alt="License: MIT" src="https://black.readthedocs.io/en/stable/_static/license.svg"></a>
12 <a href="https://pypi.org/project/black/"><img alt="PyPI" src="https://img.shields.io/pypi/v/black"></a>
13 <a href="https://pepy.tech/project/black"><img alt="Downloads" src="https://pepy.tech/badge/black"></a>
14 <a href="https://anaconda.org/conda-forge/black/"><img alt="conda-forge" src="https://img.shields.io/conda/dn/conda-forge/black.svg?label=conda-forge"></a>
15 <a href="https://github.com/psf/black"><img alt="Code style: black" src="https://img.shields.io/badge/code%20style-black-000000.svg"></a>
18 > “Any color you like.”
20 _Black_ is the uncompromising Python code formatter. By using it, you agree to cede
21 control over minutiae of hand-formatting. In return, _Black_ gives you speed,
22 determinism, and freedom from `pycodestyle` nagging about formatting. You will save time
23 and mental energy for more important matters.
25 Blackened code looks the same regardless of the project you're reading. Formatting
26 becomes transparent after a while and you can focus on the content instead.
28 _Black_ makes code review faster by producing the smallest diffs possible.
30 Try it out now using the [Black Playground](https://black.now.sh). Watch the
31 [PyCon 2019 talk](https://youtu.be/esZLCuWs_2Y) to learn more.
35 _Contents:_ **[Installation and usage](#installation-and-usage)** |
36 **[Code style](#the-black-code-style)** | **[Pragmatism](#pragmatism)** |
37 **[pyproject.toml](#pyprojecttoml)** | **[Editor integration](#editor-integration)** |
38 **[blackd](#blackd)** | **[black-primer](#black-primer)** |
39 **[Version control integration](#version-control-integration)** |
40 **[GitHub Actions](#github-actions)** |
41 **[Ignoring unmodified files](#ignoring-unmodified-files)** | **[Used by](#used-by)** |
42 **[Testimonials](#testimonials)** | **[Show your style](#show-your-style)** |
43 **[Contributing](#contributing-to-black)** | **[Change log](#change-log)** |
44 **[Authors](#authors)**
48 ## Installation and usage
52 _Black_ can be installed by running `pip install black`. It requires Python 3.6.2+ to
53 run. If you want to format Python 2 code as well, install with
54 `pip install black[python2]`.
56 #### Install from GitHub
58 If you can't wait for the latest _hotness_ and want to install from GitHub, use:
60 `pip install git+git://github.com/psf/black`
64 To get started right away with sensible defaults:
67 black {source_file_or_directory}
70 You can run _Black_ as a package if running it as a script doesn't work:
73 python -m black {source_file_or_directory}
76 ### Command line options
78 _Black_ doesn't provide many options. You can list them by running `black --help`:
81 Usage: black [OPTIONS] [SRC]...
83 The uncompromising code formatter.
86 -c, --code TEXT Format the code passed in as a string.
87 -l, --line-length INTEGER How many characters per line to allow.
90 -t, --target-version [py27|py33|py34|py35|py36|py37|py38|py39]
91 Python versions that should be supported by
92 Black's output. [default: per-file auto-
95 --pyi Format all input files like typing stubs
96 regardless of file extension (useful when
97 piping source on standard input).
99 -S, --skip-string-normalization
100 Don't normalize string quotes or prefixes.
101 -C, --skip-magic-trailing-comma
102 Don't use trailing commas as a reason to
105 --check Don't write the files back, just return the
106 status. Return code 0 means nothing would
107 change. Return code 1 means some files
108 would be reformatted. Return code 123 means
109 there was an internal error.
111 --diff Don't write the files back, just output a
112 diff for each file on stdout.
114 --color / --no-color Show colored diff. Only applies when
117 --fast / --safe If --fast given, skip temporary sanity
118 checks. [default: --safe]
120 --include TEXT A regular expression that matches files and
121 directories that should be included on
122 recursive searches. An empty value means
123 all files are included regardless of the
124 name. Use forward slashes for directories
125 on all platforms (Windows, too). Exclusions
126 are calculated first, inclusions later.
129 --exclude TEXT A regular expression that matches files and
130 directories that should be excluded on
131 recursive searches. An empty value means no
132 paths are excluded. Use forward slashes for
133 directories on all platforms (Windows, too).
134 Exclusions are calculated first, inclusions
135 later. [default: /(\.direnv|\.eggs|\.git|\.
136 hg|\.mypy_cache|\.nox|\.tox|\.venv|\.svn|_bu
137 ild|buck-out|build|dist)/]
139 --extend-exclude TEXT Like --exclude, but adds additional files
140 and directories on top of the excluded
141 ones (useful if you simply want to add to
144 --force-exclude TEXT Like --exclude, but files and directories
145 matching this regex will be excluded even
146 when they are passed explicitly as
150 --stdin-filename TEXT The name of the file when passing it through
151 stdin. Useful to make sure Black will
152 respect --force-exclude option on some
153 editors that rely on using stdin.
155 -q, --quiet Don't emit non-error messages to stderr.
156 Errors are still emitted; silence those with
159 -v, --verbose Also emit messages to stderr about files
160 that were not changed or were ignored due to
163 --version Show the version and exit.
164 --config FILE Read configuration from FILE path.
165 -h, --help Show this message and exit.
168 _Black_ is a well-behaved Unix-style command-line tool:
170 - it does nothing if no sources are passed to it;
171 - it will read from standard input and write to standard output if `-` is used as the
173 - it only outputs messages to users on standard error;
174 - exits with code 0 unless an internal error occurred (or `--check` was used).
176 ### Using _Black_ with other tools
178 While _Black_ enforces formatting that conforms to PEP 8, other tools may raise warnings
179 about _Black_'s changes or will overwrite _Black_'s changes. A good example of this is
180 [isort](https://pypi.org/p/isort). Since _Black_ is barely configurable, these tools
181 should be configured to neither warn about nor overwrite _Black_'s changes.
183 Actual details on _Black_ compatible configurations for various tools can be found in
184 [compatible_configs](https://github.com/psf/black/blob/master/docs/compatible_configs.md#black-compatible-configurations).
186 ### Migrating your code style without ruining git blame
188 A long-standing argument against moving to automated code formatters like _Black_ is
189 that the migration will clutter up the output of `git blame`. This was a valid argument,
190 but since Git version 2.23, Git natively supports
191 [ignoring revisions in blame](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revltrevgt)
192 with the `--ignore-rev` option. You can also pass a file listing the revisions to ignore
193 using the `--ignore-revs-file` option. The changes made by the revision will be ignored
194 when assigning blame. Lines modified by an ignored revision will be blamed on the
195 previous revision that modified those lines.
197 So when migrating your project's code style to _Black_, reformat everything and commit
198 the changes (preferably in one massive commit). Then put the full 40 characters commit
199 identifier(s) into a file.
202 # Migrate code style to Black
203 5b4ab991dede475d393e9d69ec388fd6bd949699
206 Afterwards, you can pass that file to `git blame` and see clean and meaningful blame
210 $ git blame important.py --ignore-revs-file .git-blame-ignore-revs
211 7a1ae265 (John Smith 2019-04-15 15:55:13 -0400 1) def very_important_function(text, file):
212 abdfd8b0 (Alice Doe 2019-09-23 11:39:32 -0400 2) text = text.lstrip()
213 7a1ae265 (John Smith 2019-04-15 15:55:13 -0400 3) with open(file, "r+") as f:
214 7a1ae265 (John Smith 2019-04-15 15:55:13 -0400 4) f.write(formatted)
217 You can even configure `git` to automatically ignore revisions listed in a file on every
221 $ git config blame.ignoreRevsFile .git-blame-ignore-revs
224 **The one caveat is that GitHub and GitLab do not yet support ignoring revisions using
225 their native UI of blame.** So blame information will be cluttered with a reformatting
226 commit on those platforms. (If you'd like this feature, there's an open issue for
227 [GitLab](https://gitlab.com/gitlab-org/gitlab/-/issues/31423) and please let GitHub
230 ### NOTE: This is a beta product
232 _Black_ is already [successfully used](https://github.com/psf/black#used-by) by many
233 projects, small and big. It also sports a decent test suite. However, it is still very
234 new. Things will probably be wonky for a while. This is made explicit by the "Beta"
235 trove classifier, as well as by the "b" in the version number. What this means for you
236 is that **until the formatter becomes stable, you should expect some formatting to
237 change in the future**. That being said, no drastic stylistic changes are planned,
238 mostly responses to bug reports.
240 Also, as a temporary safety measure, _Black_ will check that the reformatted code still
241 produces a valid AST that is equivalent to the original. This slows it down. If you're
242 feeling confident, use `--fast`.
244 ## The _Black_ code style
246 _Black_ is a PEP 8 compliant opinionated formatter. _Black_ reformats entire files in
247 place. It is not configurable. It doesn't take previous formatting into account. Your
248 main option of configuring _Black_ is that it doesn't reformat blocks that start with
249 `# fmt: off` and end with `# fmt: on`, or lines that ends with `# fmt: skip`. Pay
250 attention that `# fmt: on/off` have to be on the same level of indentation. To learn
251 more about _Black_'s opinions, to go
252 [the_black_code_style](https://github.com/psf/black/blob/master/docs/the_black_code_style.md).
254 Please refer to this document before submitting an issue. What seems like a bug might be
259 Early versions of _Black_ used to be absolutist in some respects. They took after its
260 initial author. This was fine at the time as it made the implementation simpler and
261 there were not many users anyway. Not many edge cases were reported. As a mature tool,
262 _Black_ does make some exceptions to rules it otherwise holds. This
263 [section](https://github.com/psf/black/blob/master/docs/the_black_code_style.md#pragmatism)
264 of `the_black_code_style` describes what those exceptions are and why this is the case.
266 Please refer to this document before submitting an issue just like with the document
267 above. What seems like a bug might be intended behaviour.
271 _Black_ is able to read project-specific default values for its command line options
272 from a `pyproject.toml` file. This is especially useful for specifying custom
273 `--include` and `--exclude`/`--extend-exclude` patterns for your project.
275 **Pro-tip**: If you're asking yourself "Do I need to configure anything?" the answer is
276 "No". _Black_ is all about sensible defaults.
278 ### What on Earth is a `pyproject.toml` file?
280 [PEP 518](https://www.python.org/dev/peps/pep-0518/) defines `pyproject.toml` as a
281 configuration file to store build system requirements for Python projects. With the help
282 of tools like [Poetry](https://python-poetry.org/) or
283 [Flit](https://flit.readthedocs.io/en/latest/) it can fully replace the need for
284 `setup.py` and `setup.cfg` files.
286 ### Where _Black_ looks for the file
288 By default _Black_ looks for `pyproject.toml` starting from the common base directory of
289 all files and directories passed on the command line. If it's not there, it looks in
290 parent directories. It stops looking when it finds the file, or a `.git` directory, or a
291 `.hg` directory, or the root of the file system, whichever comes first.
293 If you're formatting standard input, _Black_ will look for configuration starting from
294 the current working directory.
296 You can use a "global" configuration, stored in a specific location in your home
297 directory. This will be used as a fallback configuration, that is, it will be used if
298 and only if _Black_ doesn't find any configuration as mentioned above. Depending on your
299 operating system, this configuration file should be stored as:
301 - Windows: `~\.black`
302 - Unix-like (Linux, MacOS, etc.): `$XDG_CONFIG_HOME/black` (`~/.config/black` if the
303 `XDG_CONFIG_HOME` environment variable is not set)
305 Note that these are paths to the TOML file itself (meaning that they shouldn't be named
306 as `pyproject.toml`), not directories where you store the configuration. Here, `~`
307 refers to the path to your home directory. On Windows, this will be something like
308 `C:\\Users\UserName`.
310 You can also explicitly specify the path to a particular file that you want with
311 `--config`. In this situation _Black_ will not look for any other file.
313 If you're running with `--verbose`, you will see a blue message if a file was found and
316 Please note `blackd` will not use `pyproject.toml` configuration.
318 ### Configuration format
320 As the file extension suggests, `pyproject.toml` is a
321 [TOML](https://github.com/toml-lang/toml) file. It contains separate sections for
322 different tools. _Black_ is using the `[tool.black]` section. The option keys are the
323 same as long names of options on the command line.
325 Note that you have to use single-quoted strings in TOML for regular expressions. It's
326 the equivalent of r-strings in Python. Multiline strings are treated as verbose regular
327 expressions by Black. Use `[ ]` to denote a significant space character.
330 <summary>Example <code>pyproject.toml</code></summary>
335 target-version = ['py37']
338 # A regex preceded with ^/ will apply only to files and directories
339 # in the root of the project.
340 ^/foo.py # exclude a file named foo.py in the root of the project (in addition to the defaults)
348 Command-line options have defaults that you can see in `--help`. A `pyproject.toml` can
349 override those defaults. Finally, options provided by the user on the command line
352 _Black_ will only ever use one `pyproject.toml` file during an entire run. It doesn't
353 look for multiple files, and doesn't compose configuration from different levels of the
356 ## Editor integration
358 _Black_ can be integrated into many editors with plugins. They let you run _Black_ on
359 your code with the ease of doing it in your editor. To get started using _Black_ in your
360 editor of choice, please see
361 [editor_integration](https://github.com/psf/black/blob/master/docs/editor_integration.md).
363 Patches are welcome for editors without an editor integration or plugin! More
364 information can be found in
365 [editor_integration](https://github.com/psf/black/blob/master/docs/editor_integration.md#other-editors).
369 `blackd` is a small HTTP server that exposes Black's functionality over a simple
370 protocol. The main benefit of using it is to avoid paying the cost of starting up a new
371 Black process every time you want to blacken a file. Please refer to
372 [blackd](https://github.com/psf/black/blob/master/docs/blackd.md) to get the ball
377 `black-primer` is a tool built for CI (and humans) to have _Black_ `--check` a number of
378 (configured in `primer.json`) Git accessible projects in parallel.
379 [black_primer](https://github.com/psf/black/blob/master/docs/black_primer.md) has more
380 information regarding its usage and configuration.
382 (A PR adding Mercurial support will be accepted.)
384 ## Version control integration
386 Use [pre-commit](https://pre-commit.com/). Once you
387 [have it installed](https://pre-commit.com/#install), add this to the
388 `.pre-commit-config.yaml` in your repository:
392 - repo: https://github.com/psf/black
393 rev: 20.8b1 # Replace by any tag/version: https://github.com/psf/black/tags
396 language_version: python3 # Should be a command that runs python3.6+
399 Then run `pre-commit install` and you're ready to go.
401 Avoid using `args` in the hook. Instead, store necessary configuration in
402 `pyproject.toml` so that editors and command-line usage of Black all behave consistently
403 for your project. See _Black_'s own
404 [pyproject.toml](https://github.com/psf/black/blob/master/pyproject.toml) for an
407 If you're already using Python 3.7, switch the `language_version` accordingly. Finally,
408 `stable` is a branch that tracks the latest release on PyPI. If you'd rather run on
409 master, this is also an option.
413 Create a file named `.github/workflows/black.yml` inside your repository with:
418 on: [push, pull_request]
422 runs-on: ubuntu-latest
424 - uses: actions/checkout@v2
425 - uses: actions/setup-python@v2
426 - uses: psf/black@stable
435 **optional**: Black input arguments. Defaults to `. --check --diff`.
437 ## Ignoring unmodified files
439 _Black_ remembers files it has already formatted, unless the `--diff` flag is used or
440 code is passed via standard input. This information is stored per-user. The exact
441 location of the file depends on the _Black_ version and the system on which _Black_ is
442 run. The file is non-portable. The standard location on common operating systems is:
445 `C:\\Users\<username>\AppData\Local\black\black\Cache\<version>\cache.<line-length>.<file-mode>.pickle`
447 `/Users/<username>/Library/Caches/black/<version>/cache.<line-length>.<file-mode>.pickle`
449 `/home/<username>/.cache/black/<version>/cache.<line-length>.<file-mode>.pickle`
451 `file-mode` is an int flag that determines whether the file was formatted as 3.6+ only,
452 as .pyi, and whether string normalization was omitted.
454 To override the location of these files on macOS or Linux, set the environment variable
455 `XDG_CACHE_HOME` to your preferred location. For example, if you want to put the cache
456 in the directory you're running _Black_ from, set `XDG_CACHE_HOME=.cache`. _Black_ will
457 then write the above files to `.cache/black/<version>/`.
461 The following notable open-source projects trust _Black_ with enforcing a consistent
462 code style: pytest, tox, Pyramid, Django Channels, Hypothesis, attrs, SQLAlchemy,
463 Poetry, PyPA applications (Warehouse, Bandersnatch, Pipenv, virtualenv), pandas, Pillow,
464 every Datadog Agent Integration, Home Assistant, Zulip.
466 The following organizations use _Black_: Facebook, Dropbox, Mozilla, Quora.
468 Are we missing anyone? Let us know.
473 [writer](https://smile.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=dusty+phillips):
475 > _Black_ is opinionated so you don't have to be.
477 **Hynek Schlawack**, [creator of `attrs`](https://www.attrs.org/), core developer of
480 > An auto-formatter that doesn't suck is all I want for Xmas!
482 **Carl Meyer**, [Django](https://www.djangoproject.com/) core developer:
484 > At least the name is good.
486 **Kenneth Reitz**, creator of [`requests`](http://python-requests.org/) and
487 [`pipenv`](https://readthedocs.org/projects/pipenv/):
489 > This vastly improves the formatting of our code. Thanks a ton!
493 Use the badge in your project's README.md:
496 [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
499 Using the badge in README.rst:
502 .. image:: https://img.shields.io/badge/code%20style-black-000000.svg
503 :target: https://github.com/psf/black
507 [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
513 ## Contributing to _Black_
515 In terms of inspiration, _Black_ is about as configurable as _gofmt_. This is
518 Bug reports and fixes are always welcome! However, before you suggest a new feature or
519 configuration knob, ask yourself why you want it. If it enables better integration with
520 some workflow, fixes an inconsistency, speeds things up, and so on - go for it! On the
521 other hand, if your answer is "because I don't like a particular formatting" then you're
522 not ready to embrace _Black_ yet. Such changes are unlikely to get accepted. You can
523 still try but prepare to be disappointed.
525 More details can be found in
526 [CONTRIBUTING](https://github.com/psf/black/blob/master/CONTRIBUTING.md).
530 The log's become rather long. It moved to its own file.
532 See [CHANGES](https://github.com/psf/black/blob/master/CHANGES.md).
536 Glued together by [Łukasz Langa](mailto:lukasz@langa.pl).
538 Maintained with [Carol Willing](mailto:carolcode@willingconsulting.com),
539 [Carl Meyer](mailto:carl@oddbird.net),
540 [Jelle Zijlstra](mailto:jelle.zijlstra@gmail.com),
541 [Mika Naylor](mailto:mail@autophagy.io),
542 [Zsolt Dollenstein](mailto:zsol.zsol@gmail.com), and
543 [Cooper Lees](mailto:me@cooperlees.com).
545 Multiple contributions by:
547 - [Abdur-Rahmaan Janhangeer](mailto:arj.python@gmail.com)
548 - [Adam Johnson](mailto:me@adamj.eu)
549 - [Adam Williamson](mailto:adamw@happyassassin.net)
550 - [Alexander Huynh](mailto:github@grande.coffee)
551 - [Alex Vandiver](mailto:github@chmrr.net)
552 - [Allan Simon](mailto:allan.simon@supinfo.com)
553 - Anders-Petter Ljungquist
554 - [Andrew Thorp](mailto:andrew.thorp.dev@gmail.com)
555 - [Andrew Zhou](mailto:andrewfzhou@gmail.com)
556 - [Andrey](mailto:dyuuus@yandex.ru)
557 - [Andy Freeland](mailto:andy@andyfreeland.net)
558 - [Anthony Sottile](mailto:asottile@umich.edu)
559 - [Arjaan Buijk](mailto:arjaan.buijk@gmail.com)
560 - [Arnav Borbornah](mailto:arnavborborah11@gmail.com)
561 - [Artem Malyshev](mailto:proofit404@gmail.com)
562 - [Asger Hautop Drewsen](mailto:asgerdrewsen@gmail.com)
563 - [Augie Fackler](mailto:raf@durin42.com)
564 - [Aviskar KC](mailto:aviskarkc10@gmail.com)
566 - [Benjamin Wohlwend](mailto:bw@piquadrat.ch)
567 - [Benjamin Woodruff](mailto:github@benjam.info)
568 - [Bharat Raghunathan](mailto:bharatraghunthan9767@gmail.com)
569 - [Brandt Bucher](mailto:brandtbucher@gmail.com)
570 - [Brett Cannon](mailto:brett@python.org)
571 - [Bryan Bugyi](mailto:bryan.bugyi@rutgers.edu)
572 - [Bryan Forbes](mailto:bryan@reigndropsfall.net)
573 - [Calum Lind](mailto:calumlind@gmail.com)
574 - [Charles](mailto:peacech@gmail.com)
576 - [Christian Clauss](mailto:cclauss@bluewin.ch)
577 - [Christian Heimes](mailto:christian@python.org)
578 - [Chuck Wooters](mailto:chuck.wooters@microsoft.com)
579 - [Chris Rose](mailto:offline@offby1.net)
581 - [Cong](mailto:congusbongus@gmail.com)
582 - [Cooper Ry Lees](mailto:me@cooperlees.com)
583 - [Dan Davison](mailto:dandavison7@gmail.com)
584 - [Daniel Hahler](mailto:github@thequod.de)
585 - [Daniel M. Capella](mailto:polycitizen@gmail.com)
587 - [David Hotham](mailto:david.hotham@metaswitch.com)
588 - [David Lukes](mailto:dafydd.lukes@gmail.com)
589 - [David Szotten](mailto:davidszotten@gmail.com)
590 - [Denis Laxalde](mailto:denis@laxalde.org)
591 - [Douglas Thor](mailto:dthor@transphormusa.com)
593 - [Eli Treuherz](mailto:eli@treuherz.com)
594 - [Emil Hessman](mailto:emil@hessman.se)
595 - [Felix Kohlgrüber](mailto:felix.kohlgrueber@gmail.com)
596 - [Florent Thiery](mailto:fthiery@gmail.com)
598 - [Giacomo Tagliabue](mailto:giacomo.tag@gmail.com)
599 - [Greg Gandenberger](mailto:ggandenberger@shoprunner.com)
600 - [Gregory P. Smith](mailto:greg@krypto.org)
603 - [Hadi Alqattan](mailto:alqattanhadizaki@gmail.com)
604 - [Heaford](mailto:dan@heaford.com)
605 - [Hugo Barrera](mailto::hugo@barrera.io)
607 - [Hynek Schlawack](mailto:hs@ox.cx)
608 - [Ivan Katanić](mailto:ivan.katanic@gmail.com)
609 - [Jakub Kadlubiec](mailto:jakub.kadlubiec@skyscanner.net)
610 - [Jakub Warczarek](mailto:jakub.warczarek@gmail.com)
611 - [Jan Hnátek](mailto:jan.hnatek@gmail.com)
612 - [Jason Fried](mailto:me@jasonfried.info)
613 - [Jason Friedland](mailto:jason@friedland.id.au)
614 - [jgirardet](mailto:ijkl@netc.fr)
616 - [Jimmy Jia](mailto:tesrin@gmail.com)
617 - [Joe Antonakakis](mailto:jma353@cornell.edu)
618 - [Jon Dufresne](mailto:jon.dufresne@gmail.com)
619 - [Jonas Obrist](mailto:ojiidotch@gmail.com)
620 - [Jonty Wareing](mailto:jonty@jonty.co.uk)
621 - [Jose Nazario](mailto:jose.monkey.org@gmail.com)
622 - [Joseph Larson](mailto:larson.joseph@gmail.com)
623 - [Josh Bode](mailto:joshbode@fastmail.com)
624 - [Josh Holland](mailto:anowlcalledjosh@gmail.com)
625 - [Joshua Cannon](mailto:joshdcannon@gmail.com)
626 - [José Padilla](mailto:jpadilla@webapplicate.com)
627 - [Juan Luis Cano Rodríguez](mailto:hello@juanlu.space)
628 - [kaiix](mailto:kvn.hou@gmail.com)
629 - [Katie McLaughlin](mailto:katie@glasnt.com)
631 - [Keith Smiley](mailto:keithbsmiley@gmail.com)
632 - [Kenyon Ralph](mailto:kenyon@kenyonralph.com)
633 - [Kevin Kirsche](mailto:Kev.Kirsche+GitHub@gmail.com)
634 - [Kyle Hausmann](mailto:kyle.hausmann@gmail.com)
635 - [Kyle Sunden](mailto:sunden@wisc.edu)
637 - [Linus Groh](mailto:mail@linusgroh.de)
638 - [Loren Carvalho](mailto:comradeloren@gmail.com)
639 - [Luka Sterbic](mailto:luka.sterbic@gmail.com)
640 - [LukasDrude](mailto:mail@lukas-drude.de)
643 - [Matt VanEseltine](mailto:vaneseltine@gmail.com)
644 - [Matthew Clapp](mailto:itsayellow+dev@gmail.com)
645 - [Matthew Walster](mailto:matthew@walster.org)
647 - [Michael Aquilina](mailto:michaelaquilina@gmail.com)
648 - [Michael Flaxman](mailto:michael.flaxman@gmail.com)
649 - [Michael J. Sullivan](mailto:sully@msully.net)
650 - [Michael McClimon](mailto:michael@mcclimon.org)
651 - [Miguel Gaiowski](mailto:miggaiowski@gmail.com)
652 - [Mike](mailto:roshi@fedoraproject.org)
653 - [mikehoyio](mailto:mikehoy@gmail.com)
654 - [Min ho Kim](mailto:minho42@gmail.com)
655 - [Miroslav Shubernetskiy](mailto:miroslav@miki725.com)
657 - [Nathan Goldbaum](mailto:ngoldbau@illinois.edu)
658 - [Nathan Hunt](mailto:neighthan.hunt@gmail.com)
659 - [Neraste](mailto:neraste.herr10@gmail.com)
660 - [Nikolaus Waxweiler](mailto:madigens@gmail.com)
661 - [Ofek Lev](mailto:ofekmeister@gmail.com)
662 - [Osaetin Daniel](mailto:osaetindaniel@gmail.com)
663 - [otstrel](mailto:otstrel@gmail.com)
664 - [Pablo Galindo](mailto:Pablogsal@gmail.com)
665 - [Paul Ganssle](mailto:p.ganssle@gmail.com)
666 - [Paul Meinhardt](mailto:mnhrdt@gmail.com)
667 - [Peter Bengtsson](mailto:mail@peterbe.com)
668 - [Peter Grayson](mailto:pete@jpgrayson.net)
669 - [Peter Stensmyr](mailto:peter.stensmyr@gmail.com)
671 - [Quentin Pradet](mailto:quentin@pradet.me)
672 - [Ralf Schmitt](mailto:ralf@systemexit.de)
673 - [Ramón Valles](mailto:mroutis@protonmail.com)
674 - [Richard Fearn](mailto:richardfearn@gmail.com)
676 - [Rishikesh Jha](mailto:rishijha424@gmail.com)
677 - [Rupert Bedford](mailto:rupert@rupertb.com)
679 - [Rémi Verschelde](mailto:rverschelde@gmail.com)
680 - [Sami Salonen](mailto:sakki@iki.fi)
681 - [Samuel Cormier-Iijima](mailto:samuel@cormier-iijima.com)
682 - [Sanket Dasgupta](mailto:sanketdasgupta@gmail.com)
684 - [Scott Stevenson](mailto:scott@stevenson.io)
686 - [shaoran](mailto:shaoran@sakuranohana.org)
687 - [Shinya Fujino](mailto:shf0811@gmail.com)
689 - [Stavros Korokithakis](mailto:hi@stavros.io)
690 - [Stephen Rosen](mailto:sirosen@globus.org)
691 - [Steven M. Vascellaro](mailto:S.Vascellaro@gmail.com)
692 - [Sunil Kapil](mailto:snlkapil@gmail.com)
693 - [Sébastien Eustace](mailto:sebastien.eustace@gmail.com)
694 - [Tal Amuyal](mailto:TalAmuyal@gmail.com)
695 - [Terrance](mailto:git@terrance.allofti.me)
696 - [Thom Lu](mailto:thomas.c.lu@gmail.com)
697 - [Thomas Grainger](mailto:tagrain@gmail.com)
698 - [Tim Gates](mailto:tim.gates@iress.com)
699 - [Tim Swast](mailto:swast@google.com)
700 - [Timo](mailto:timo_tk@hotmail.com)
702 - [Tom Christie](mailto:tom@tomchristie.com)
703 - [Tony Narlock](mailto:tony@git-pull.com)
704 - [Tsuyoshi Hombashi](mailto:tsuyoshi.hombashi@gmail.com)
705 - [Tushar Chandra](mailto:tusharchandra2018@u.northwestern.edu)
706 - [Tzu-ping Chung](mailto:uranusjr@gmail.com)
707 - [Utsav Shah](mailto:ukshah2@illinois.edu)
710 - [Ville Skyttä](mailto:ville.skytta@iki.fi)
711 - [Vishwas B Sharma](mailto:sharma.vishwas88@gmail.com)
712 - [Vlad Emelianov](mailto:volshebnyi@gmail.com)
713 - [williamfzc](mailto:178894043@qq.com)
714 - [wouter bolsterlee](mailto:wouter@bolsterl.ee)
716 - [Yngve Høiseth](mailto:yngve@hoiseth.net)
717 - [Yurii Karabas](mailto:1998uriyyo@gmail.com)
718 - [Zac Hatfield-Dodds](mailto:zac@zhd.dev)