Staging
v0.5.1
v0.5.1
Revision f526d10267e8c0d20b3f5584eb7ca671f3a526df authored by Miss Islington (bot) on 20 July 2020, 11:35:11 UTC, committed by GitHub on 20 July 2020, 11:35:11 UTC
Just a simple documentation fix: apply_async and map_async return a "multiprocessing.pool.AsyncResult Object", not a "result object". (cherry picked from commit f9bf0157999cb4adbcfd7e9bf526bfa48601e128) Co-authored-by: Volker-Weissmann <39418860+Volker-Weissmann@users.noreply.github.com>
1 parent 58f59a9
CODE_OF_CONDUCT.md
# Code of Conduct
Please note that all interactions on
[Python Software Foundation](https://www.python.org/psf-landing/)-supported
infrastructure is [covered](https://www.python.org/psf/records/board/minutes/2014-01-06/#management-of-the-psfs-web-properties)
by the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/),
which includes all the infrastructure used in the development of Python itself
(e.g. mailing lists, issue trackers, GitHub, etc.).
In general, this means that everyone is expected to be **open**, **considerate**, and
**respectful** of others no matter what their position is within the project.
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...