Contact and corrections

Spotted a wrong line in one of our guides? Tell us. Four Spaces is run on a small scale and independently, so we have no capacity to troubleshoot your own Python projects.

Reporting an error

If you find a wrong statement, an example that no longer behaves as shown, a tool option that has changed or a broken source link, please write to Four Spaces at the postal address shown on the legal notice page. Quote the page address and the sentence concerned and, if possible, the documentation that shows the correct information. When a page is corrected, its "Updated" date changes.

Checker results

If the style checker reports something that pycodestyle does not, or misses something it reports, include the smallest snippet that shows the difference and the pycodestyle version you compared with. Please do not send confidential code.

What we cannot help with

• Reviewing or debugging your code. Python's community forums and the issue trackers of the tools concerned are the right places.
• Bug reports for pycodestyle, flake8, pylint, black, ruff or other tools. Each project has its own issue tracker; Four Spaces is not connected to any of them.
• Paid placement. No tool vendor can buy a mention, a link or a sponsored article on Four Spaces.
• The former "PEP8 online" tool. If you are after the old checker, we cannot help: Four Spaces is unrelated to it and never had its source, its stored data or any results people shared through it. About has the background.