From a7271b275088a54f5ba2cfd0675f8ca0f27aae1e Mon Sep 17 00:00:00 2001 From: Diego Ramirez Date: Mon, 11 Apr 2022 12:45:38 -0500 Subject: [PATCH] Fix a badly-formatted Python block in the docs The whole block is indented, though a code block with Python formatting is there. --- docs/faq.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index e07fc1e5..5d8aa71b 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -206,30 +206,30 @@ these steps into your package's build process. For example, if you're using setuptools, you can add steps to your package's `setup.py` using a structure like this: - ```python - import subprocess - import setuptools - import setuptools.command.build_py +```python +import subprocess +import setuptools +import setuptools.command.build_py - class BuildPyCommand(setuptools.command.build_py.build_py): - """Custom build command.""" +class BuildPyCommand(setuptools.command.build_py.build_py): + """Custom build command.""" - def run(self): + def run(self): # your custom build steps here # e.g. # subprocess.run(['python', 'scripts/my_custom_script.py'], check=True) setuptools.command.build_py.build_py.run(self) - setuptools.setup( - cmdclass={ - 'build_py': BuildPyCommand, - }, - # Usual setup() args. - # ... - ) - ``` +setuptools.setup( + cmdclass={ + 'build_py': BuildPyCommand, + }, + # Usual setup() args. + # ... +) +``` #### Compiler flags